Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate Changing Recipe Registration #74

Open
starcraftman opened this issue Jan 20, 2016 · 0 comments
Open

Investigate Changing Recipe Registration #74

starcraftman opened this issue Jan 20, 2016 · 0 comments
Assignees
Milestone

Comments

@starcraftman
Copy link
Owner

Current recipe database model is:

  • Folder has bunch of recipes.
  • Import every one and scan for first Recipe subclass and index it.

A better idea I think is:

  • Folder has a bunch of recipes.
  • Each recipes has 1 or more recipes.
  • Each recipe is decorated by a decorator of form:
  • Class decorator could handle the common manipulations/decorations of the build/verify methods.
@RegisterRecipe
class Ag(Recipe):
....
@starcraftman starcraftman self-assigned this Jan 20, 2016
@starcraftman starcraftman added this to the 0.3 milestone Jan 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant