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
I might have a solution proposed for this. The solution will be only on frontend side of app, so there is no need to have a changes in backend.
The frontend will create a modal form for schedule name as the design proposed.
but since we've already had API for renaming the schedule (separate from the create schedule API).
on frontend we can just send renaming request, after successfully creating the schedule. We'll have schedule id after create and be able to rename the schedule. This can be achieved by chaining renaming requests asynchronously only after creating schedule is finished.
Therefore we don't need to have any addition or edit for the API service in backend.
But, for sure having Create Schedule API able to recieve the schedule name in request body might be the convenient way also, since it will request once per schedule create rather than 2 API request.
This issue is a:
Current behavior:
As of now, every schedules are automatically named as 'Untitled' after it is saved. It can only be renamed after you open the schedule detail page.
Requested behavior:
The design team from Ristek proposed that it would be better if user get the chance to give each schedules' name before (and not after) saving it.
Related Issue:
Also see this issue on SusunJadwal's backend repository:
ristekoss/susunjadwal-backend#9
Why this behavior is better:
It is suggested by Ristek's design team that this would lead to a better and more coherent user flow.
The text was updated successfully, but these errors were encountered: