Meta information on recipe #35

Closed
opened 2019-04-29 18:53:01 +00:00 by root · 6 comments
root commented 2019-04-29 18:53:01 +00:00 (Migrated from dev.cryptec.at)

A recipe should contain a meta field, maybe even a short description containing the origin or history of a recipe. Dunno how much a field like this could be abused for unnecessary information, etc.

A recipe should contain a meta field, maybe even a short description containing the origin or history of a recipe. Dunno how much a field like this could be abused for unnecessary information, etc.
root commented 2019-04-29 18:53:01 +00:00 (Migrated from dev.cryptec.at)

changed milestone to %1

changed milestone to %1
david commented 2019-05-24 18:23:37 +00:00 (Migrated from dev.cryptec.at)

So something like an "abstract*, e. g.:

Title: Lintil Soup
Abstract: Tasty lintil soup with fennel

?

So something like an "abstract*, e. g.: Title: Lintil Soup Abstract: Tasty lintil soup with fennel ?
root commented 2019-07-24 07:53:28 +00:00 (Migrated from dev.cryptec.at)

created merge request !126 to address this issue

created merge request !126 to address this issue
root commented 2019-07-24 07:53:28 +00:00 (Migrated from dev.cryptec.at)

mentioned in merge request !126

mentioned in merge request !126
david commented 2019-07-24 18:57:14 +00:00 (Migrated from dev.cryptec.at)

closed via merge request !126

closed via merge request !126
david commented 2019-07-24 18:57:15 +00:00 (Migrated from dev.cryptec.at)

mentioned in commit 75073c385a

mentioned in commit 75073c385a9f663a4e650252ffa4a80b9109dc44
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
root/claypot#35
No description provided.