Skip to content
This repository has been archived by the owner on Jul 2, 2021. It is now read-only.

One naming convention in snapshot serializer: camel case #45

Open
gladky opened this issue Oct 25, 2016 · 2 comments
Open

One naming convention in snapshot serializer: camel case #45

gladky opened this issue Oct 25, 2016 · 2 comments
Labels

Comments

@gladky
Copy link
Contributor

gladky commented Oct 25, 2016

I suggest we stick to one naming convention in serializers: camel case. Here is part of snapshot requested in Expert API with block_retri key.

"globalTtsStates": {
"block_retri": {
"state": "R_8",
"percentWarning": 0,
"percentBusy": 0
},
}

@gladky gladky added the bug label Oct 25, 2016
@gladky gladky assigned ghost Oct 25, 2016
@ghost
Copy link

ghost commented Oct 25, 2016

Will take care of this, thanks.

@hsakulin
Copy link

Hi,
when switching to camel case, please make sure to keep acronyms such as TTS in all caps (or all lowercase if at the start).
Hannes.


From: Maciej Gladki [[email protected]]
Sent: 25 October 2016 08:57
To: cmsdaq/DAQAggregator
Subject: [cmsdaq/DAQAggregator] One naming convention in snapshot serializer: camel case (#45)

I suggest we stick to one naming convention in serializers: camel case. Here is part of snapshot requested in Expert API with block_retri key.

"globalTtsStates": {
"block_retri": {
"state": "R_8",
"percentWarning": 0,
"percentBusy": 0
},
}


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/45, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASanSvDL02QyitDgEgAfzPDSff693iU4ks5q3ahfgaJpZM4Kfn9W.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants