-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Remove] /iot/services
API path
#1649
Comments
15 occurrences in PR #1648 |
PR #1648 does a wrapping to use "groups" but internally "services" is still used in the code. Eg:
instead of
That should be changed, the same (non-obsolete) term used in the API (groups) should be used internally in the code. The code is more maintainable if API terms and code terms are aligned. This task should be done as part of this issue or as part of issue #1587 (considering also the alignment with the DB model, so completing alignment API-code-DB). |
Maybe both #1587 and this issue should be addressed together. |
I agree. When internal datamodels align with DB models, group term should be used. At this point, work made in #1648 will not be useful anymore and code with #FIXME1649 can be deleted. The following tasks should be addressed:
|
Ensure also the following issues (in other repositories) has been accomplished before removing the deprecated routes: |
With issue #752 and PR #1648 , the usage of API route
/iot/services
is deprecated, and, eventually, should be removedLook for
#FIXME1649
in the code for references that should be removedThe text was updated successfully, but these errors were encountered: