-
Notifications
You must be signed in to change notification settings - Fork 12.5k
[CAL-2924] [bug] events can be saved even if it is as same as before #13112
Copy link
Copy link
Open
Labels
Low priorityCreated by Linear-GitHub SyncCreated by Linear-GitHub SyncStalecommunityCreated by Linear-GitHub SyncCreated by Linear-GitHub Syncuiarea: UI, frontend, button, form, inputarea: UI, frontend, button, form, input⚡ Quick WinsA collection of quick wins/quick fixes that are less than 30 minutes of workA collection of quick wins/quick fixes that are less than 30 minutes of work
Description
Found a bug? Please fill out the sections below. 👍
Issue Summary
User can update already created events, but we can click 'save' button even if user hasn't updated any of fields.
Steps to Reproduce
- Create event if don't have any.
- Navigate to the event
- You will be able to save and it will really make a fetch request even if you haven't updated any field
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Actual Results
Right now, save button is working even if any field is not updated yet.
Expected Results
Save button should be disabled if none of fields is updated yet.
Evidence
Screen.Recording.2024-01-09.at.12.37.45.PM.mov
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Low priorityCreated by Linear-GitHub SyncCreated by Linear-GitHub SyncStalecommunityCreated by Linear-GitHub SyncCreated by Linear-GitHub Syncuiarea: UI, frontend, button, form, inputarea: UI, frontend, button, form, input⚡ Quick WinsA collection of quick wins/quick fixes that are less than 30 minutes of workA collection of quick wins/quick fixes that are less than 30 minutes of work