Pelican Platform
Standardize JSON casing #1734
Closed
CannonLock
started this conversation in
General
Standardize JSON casing
#1734
Replies: 1 comment 3 replies
-
|
Just talked to @jhiemstrawisc, and we will be moving forward with snake_case! |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
I just found this old issue: There it says that at one point we settled on camel case for Web UI API data. Does that mean JSON? |
Beta Was this translation helpful? Give feedback.
-
|
Ah good to know, yeah that does. |
Beta Was this translation helpful? Give feedback.
-
|
I redact the previous statement. We will be moving forward with camelCase! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Current api keys use different 4 casing standards in its json responses.
https://github.com/PelicanPlatform/pelican/blob/main/server_structs/director.go
kebab-case
PascalCase
camelCase
snake_case
It would be nice to have some pattern in our use. If that is too challenging due to the conflicting technology and standards colliding it would be great to at least remove all use of kebab-case as it is unwieldy to work with on the frontend.
Beta Was this translation helpful? Give feedback.
All reactions