-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
Food #446
base: master
Are you sure you want to change the base?
Conversation
isVegetarian?: boolean | ||
/** Flagging `isVegan` will automatically flag `isVegetarian` as true. */ | ||
isVegan?: boolean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These could probably be combined into a single attribute. Perhaps something along the lines of diet: "vegan"
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking that the simplest way to calculate veganocity would be an optional override, and then a simple if statement to check whether there were any ingredients
that broke the conduct.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, seems it might break the single source of truth principle. Perhaps we could use an isVegan
, and isVegetarian
function to check it at runtime instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, that's the plan.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And then we don't need the flags to be on the object, as they're calculated instead of explicitly set.
What does this do?
Adds a more robust food generation system.
How was this tested? Did you test the changes in the compiled
.html
file?Still in draft.
Is there a GitHub Issue that this is resolving?
Closes #70.