ProfessionalWiki / ProfessionalWiki/AutomatedValues
Product question: when to hide label editing
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Premise: It does not make sense to show label editing UI in cases where labels are automatically generated. After all, when someone uses the editing UI, their edit will just be overridden by generated value.
"buildLabel": {
"en": {
"P2": "$"
},
"de": {
"P2": "$"
}
},
Question: in case of the above rule applying to the entity, which labels do we prevent editing for? Just the English and German ones? Or all labels?
Further question: does it typically even make sense for people to be able to add labels in other languages in the types of wikis where rules are used to generate labels? Perhaps it is typically better to restrict label editing to the language or languages the dataset is officially maintained in.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. First resolve whether generated labels should disable editing only in the listed languages or in all languages, and whether additional-language labels should be allowed. Done means documenting and implementing an agreed product rule with corresponding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100