openlibhums / openlibhums/janeway
Submission Fields: Content of the field can no longer be removed after it has been filled
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Our journals are using additional submission fields as a workaround to display the names of the reviewers on the article page below the table of contents.
We have now established the following: As soon as the field has been filled in, the content can no longer be removed, only replaced by other content. It then becomes a mandatory field, so to speak. Deleting the content is ignored.
JW Version: 1.7.4
Parameters of the field:
- Kind: Text Field
- Width: Third
- Display: true
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Reproduce the problem with a displayed Text Field configured to one-third width, then trace how its value is saved and cleared; done means an existing value can be deleted rather than only replaced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100