You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently data is stored for weekend students only. But those are not specified as weekend. Then which format to follow when adding weekend time tables? Denote weekend batches from negatives (ex: -01 means WE batch 1 of given specialization) is an one option.
Else we have to refactor the entire data.json to make it compatible with weekend as well. That is very work intensive. So i would not recommend that.
Then add another field in the home page as Batch type or something like that. That will choose between weekdays and weekend. So items under sub group can be dynamically inserted according to that choice.
The text was updated successfully, but these errors were encountered:
Currently, weekend batches are added as well, inside each specialization, just same as a normal subgroup. I used the prefix WE in front of the group number. (only added in SE for now). An image is attached below.
Update:
Ideas / suggestions are welcome based on this
Yes, you guy developing it pretty fast. I almost missed that :). Btw you can just provide the commit like this. So no need to get screenshots. And it helps to track everything.
Currently data is stored for weekend students only. But those are not specified as weekend. Then which format to follow when adding weekend time tables? Denote weekend batches from negatives (ex: -01 means WE batch 1 of given specialization) is an one option.
Else we have to refactor the entire
data.json
to make it compatible with weekend as well. That is very work intensive. So i would not recommend that.Then add another field in the home page as
Batch type
or something like that. That will choose between weekdays and weekend. So items under sub group can be dynamically inserted according to that choice.The text was updated successfully, but these errors were encountered: