Edit metadata API: doesn't add or replace if the value "contains" the current value
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Using the edit metadata API, I tried both adding and replacing an author (note, in practice it is more likely useful as a "replace"):
Current value: Messi, Lionel
New Value: Messi, Lionel A.
Nothing happened - this is because the check uses contains logic (instead of equality) to check the metadata. This is because it is comparing to the display value which concatenates multiple fields, so we'll need to figure out a clever way to replace / fix this logic.
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
Start at the edit metadata API entry point and trace how the current metadata is converted to a display value before the contains check. Reproduce both add and replace cases using an existing value that contains the new value. Done means the API distinguishes complete metadata values and correctly adds or replaces the author without false matches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100