telefonicaid / telefonicaid/iotagent-node-lib
refactoring apis to be more compliant with restful standards
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 90
- Avg merge
- 2h 35m
- Merged PRs (30d)
- 1
Description
hi,
i think it would be good to have a v2 version of the apis that works totally based on uris.
e.g.
/v2/services/
/v2/services/{id}
/v2/services/{id}/devices
/v2/services/{id}/devices/{id}
feelings?
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
The issue names no files, tests, or entry points. Start by reviewing the existing API surface and comparing it with the proposed /v2/services/, /v2/services/{id}, and nested device URIs. Clarify the v2 scope, compatibility requirements, and acceptance criteria; done requires an agreed RESTful design before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100