Should title be mandatory in ExposedThingInit?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
@mmccool pointed out that in the new ExposedThingInit algorithm title field should not be automatically generated. This field is critically important in UIs and human-readable documents. Therefore we should encourage developers to think twice before naming their Things with random unique strings. If they really need they can still their own function for the creation of unique names. This would also provide greater flexibility in name generation.
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 by reading the ExposedThingInit algorithm and the surrounding requirements for the title field. Clarify whether titles must be supplied or only should not be generated automatically, then update the specification so the decision and expected behavior are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100