Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TO API 2.0 should use consistent field names for all the "user" endpoints #3220

Closed
rawlinp opened this issue Jan 15, 2019 · 1 comment
Closed

TO API 2.0 should use consistent field names for all the "user" endpoints #3220

rawlinp opened this issue Jan 15, 2019 · 1 comment
Labels
Traffic Ops API Next Improvements to Traffic Ops API - particularly breaking changes Traffic Ops related to Traffic Ops

Comments

@rawlinp
Copy link
Contributor

rawlinp commented Jan 15, 2019

In version 1.x, the various user endpoints use one of either "roleName" or "rolename". In TO API 2.0, all the user endpoints should use a consistent field name, "roleName". This will alleviate much confusion and will allow the various user structs to be consolidated.

For reference, see #3219, #2535, and #2846.
@rawlinp rawlinp added the Traffic Ops API Next Improvements to Traffic Ops API - particularly breaking changes label Jan 15, 2019
@mitchell852 mitchell852 added the Traffic Ops related to Traffic Ops label Nov 18, 2019
@rawlinp
Copy link
Contributor Author

rawlinp commented Dec 7, 2021

The rolename vs roleName discrepancy is fixed as of TO API v4, but #6299 is related and appears to describe even more discrepancies.

@rawlinp rawlinp closed this as completed Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Traffic Ops API Next Improvements to Traffic Ops API - particularly breaking changes Traffic Ops related to Traffic Ops
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mitchell852 @rawlinp