consistent naming: attribute vs. feature
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
The API is not entirely consistent when it comes to the terms "attribute" and "feature". The former seems to be used more frequently, but at least in the "get data features" REST API call, the same entities are referred to as features. The returned xml / json objects also use the names "features" and "feature".
Please be consistent.
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 reviewing the REST API documentation and the “get data features” call mentioned in the issue, including its XML and JSON response objects. Audit where “attribute” and “feature” are used across the API, then define the consistent terminology and verify that the affected responses and documentation agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100