mdgspace / appetizer-flutter Goto Github PK

• Don't use your own font styles and other colors, define them in theme_global.dart refer flutter theming.
• Don't combine each other branch and make a large PR, rather make many small documented PRs.
• Try to extract custom widget into a different widget or make them pass in a method.
• Documentation of each and every method that you write should be there.

Any additional points that you want to add, post them in the comments.

Text Fields and Row widget implementation

Display the Weekly menu, with a provision to view the next and the previous 4 weeks. The week dates should also be visible

QR_code needs internet to be fetched, store it offline.

if response of any API has {"detail" : "invalid token" } logout from the App

@Nitish145 Change the implementation for the ConfirmMealsScreen, SwitchMealsScreen etc. like I have done for other classes. Make it efficient. You might think that it is unimportant but it is very important in case we make any changes furthur, also these Screen complemently differ in principles of logical design from the ones I have changed it will create a lot of troubles and issues

If the font size of phone is increased UI elements such as Settings Card Overflow and disalign.

1. Start showing qr code only after the decided time window, else display grey button and an onClick toast "qr code will be available 8 hours befor the meal". (@dev-ritik how is it implemented on backend side)
2. When the qr code is open in one card and we change to next date the card's state remains to be in qr mode,

I encounter this quite often while randomly switching days.

Apart from the leave pending (Yellow), also add approved (Green), Denied (Red), Unapproved (Blue)

Add a feature to change the base URL if the current user is an Admin. This should be done at the time of login.

Signup with Channeli is not working properly. Upon doing so, no user is created in the backend and the app logs in the user directly and throws an error

Remote toggling of features from the admin panel.

The onBoarding screens haven't been implemented yet.

Checked user should not be able to create new leaves

Current app

Alpha app

Update the meal fields to include cost_type to indicate N (normal) or S (special) type

Signup should be done using Channel I OAuth.User data should be properly manipulated and stored.

Add a switch details activity navigatable from the navigation bar. Use /api/leave/switch/all/

Use theme.dart for uniformity

I don't know if the notifications I receive also comes from the alpha-Appetizer app but they always open the current app on clicking it on the notification tray.
Do write back if it requires some help from the backend as well.

Skipped meals are not displayed as such. Also, button to add feedback is not added

Current app

Alpha phase app

@aseem09 IMG has made some changes on their side, current implementation of SIGN-UP with channel I is no longer working, please solve this issue ASAP.

scrolling of date picker is continuous not discrete. if we slightly scroll date picker then do not scroll 7 days but scroll 2-3 days and then the day will be wrong with that date because day column is fixed.

switches_left has been added in the server. Add this to the mobile app as well

Switch status not changing on switch applied from your meals section

when we switch a meal with leave = true from, either of YourMenuCard or OtherMenuCard the leave status remains to be true while the meal is successfully switched.
Edit:
I got confused, thus to make every thing clear disable toggle button when a meal is in switched state

• Horizontal date picker shows some weird behaviour on switching months..
  
  

Ex- If a cancel switch request fails there is no meaning of reloading the menu..

A Monday-start based week would be better wrt sunday-start based (as in the web-interface, wherein the menu is added)

The user information is should always be fetched and rendered if possible. The current setting page in the alpha-app does not update the user info even after updating them from the backend

This is not the case when response == 404