Show popup warning to librarians when they've populated fields that have an "add" button but forgot to use the button
Problem
Most form fields on work, edition or author pages are just saved when I click "save". However, some fields (e.g. add link to work) have an additional "add" button that needs to be clicked before saving. I keep forgetting to use that button, and the input to that form field is lost.
A clear and concise description of what you want to happen
Whenever I populate a form field that has an "add button" and then save that page without having used the "add" button, I would like to see a warning.
Expected behaviour / screenshots (ex: Figma design screenshots for UI feature)
Additional Context
Proposal & Constraints
What is the proposed solution / implementation?
Show a popup warning whenever a form field with an add button has been populated but not saved. Or maybe just save the content, if that is possible.
Is there a precedent of this approach succeeding elsewhere?
Which suggestions or requirements should be considered for how feature needs to appear or be implemented?
Leads
Related files
Stakeholders
Instructions for Contributors
- Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.
hey @jimchamp I would like to work on this issue. can you please assign this to me ?
@bilch can you assign this issue to me?
@mekarpeles I'd like to work on this issue
@rebecca-shoptaw can you assign this issue to me?
@AbhinavKRN That's always a good question for the issue's lead, which you can see in the "Labels" section is @jimchamp 🙂
@jimchamp can you assign this issue to me?
Hii @jimchamp if this still issue is still not resolved, can you assign it to me? Thank you
@AbhinavKRN, can you give a progress update? If you are no longer able to work on this issue, let me know so I can reassign it.
Her @jimchamp , i want to work on this issue
No word from @AbhinavKRN, so I'm assuming that this is not being worked on. Are you still interested in working on this, @smitrami-123?
Hii @jimchamp I am interested working on the issue. You can assign it to me. Thank you
Just a quick question, is it still a good first issue? because I am new to open source contribution
@smitrami-123, this may be a good first issue, but as of now I don't think that there is enough information here for anyone to solve the issue.
In the near future, I'll update this issue with additional requirements and a list of files that will likely require changes. Until then, I'll abstain from assigning this issue to a contributor.