-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: implement nutrition data display (see #124) #136
Conversation
@@ -482,36 +484,48 @@ Additive? _convertAdditive(Enum$Additive e) { | |||
Enum$Additive.LAXATIVE_IF_OVERUSED => Additive.laxativeIfOverused, | |||
Enum$Additive.PHENYLALANINE => Additive.phenylalanine, | |||
Enum$Additive.ALCOHOL => Additive.alcohol, | |||
Enum$Additive.PRESSED_MEET => Additive.pressedMeat, | |||
Enum$Additive.PRESSED_MEAT => Additive.pressedMeat, |
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.
nutrition/logic
seems to have diverged from main
and didn't compile. Didn't want to rebase, though, because would probably be a mess when merging everything (backend and frontend) together, so I manually applied a couple of changes like this to get a working app to start with.
Could you maybe open a branch, so that we can run the tests here? I cannot run them on your fork. Then we can see why the tests are failing. |
I don't think I have permission to create branches in this repo. But you can just clone my code and run the tests locally. |
@muety Nice! I will take a closer look at that tomorow (after my exam 😉) |
Ok, some organization points first: If you like, you can also add a section for environmental information. Now to the content: For the tests, maybe @AlexKutschera or @ElenaHaeussler can help you. Recommended further proceeding
|
Thought about that as well, but would probably prefer to do that in a separate pass.
Will do!
I think from a UX perspective, the nutrition info goes quite well alongside additives and allergens, so would probably keep it inside the accordion. I didn't implement nutrition stats for sides, though. Will add that in soon.
Waiting for the backend will probably be less of a chaos, since I'll need the latest backend-side changes anyway, so will go for the second option. It's the #128, correct? Should be resolved soon-ish, I presume? Looking forward to get your feedback on my implementation and how to proceed with the tests, @AlexKutschera, @ElenaHaeussler. |
I will not have time to look at it before the end of next week. Maybe @AlexKutschera has time before then. |
alright
👍
yes. I hope so, but in the end, reviews take always longer than expected 😅 |
Sometimes it can also go fast: the new backend version is already merged to main and deployed |
Awesome! I won't be available for about a week, though, so don't be surprised if I'll only continue working on this afterwards. |
Just as a quick sign of life from my side: haven't forgot about this! Still keen to get this finished, it's just been a super busy week. Will do the remaining implementation somewhere in the next couple of days. |
Hab deinen Branch mal auf https://github.com/kronos-et-al/MensaApp/tree/nutrition/app kopiert und aus der Liste eine Tabelle gemacht, passt für den Fall besser. Muss noch die Farben fixen, die tun aktuell noch nicht ganz was ich von ihnen will |
Implement frontend-side part of #124. Tests are failing, but not sure how to go about them. Perhaps you could give me a quick intro on how testing is being done in this project?
Let me know what you think.