-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Consistency in unified sensor driver property naming #622
Comments
I've been silent on this because I haven't felt super strong about it. I thought about expanding them out ( |
@tuupola Would you like to switch them to the lower case version? |
These two libs to be changed to reflect the move to lowercase (am I forgetting any others which use the TVOC/eCO2 property naming?): |
Had missed this. @tannewt sure, I will check them out. |
Thanks @tuupola! Let me know if you need any guidance on how to get it done.
…On Sun, Mar 4, 2018 at 9:55 PM Mika Tuupola ***@***.***> wrote:
Had missed this. @tannewt <https://github.com/tannewt> sure, I will check
them out.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#622 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADNqQYJud9mHyh63V3PfX01L_sIwcaDks5tbNNmgaJpZM4SDQdk>
.
|
SGP30 is missing properties all together. They should be added. |
@mrmcwethy would you be interested in adding eco2 and tvoc properties to the SGP30 driver? |
@tannewt I would be happy to add these properies. I will need to order a sgp30 board. |
Go ahead and order one (and other other sensors of interest). I think @brentru may have started the sgp30 work though. |
Working through the SGP30 right now. @tannewt Do we want properties for the baseline sensor readings (would be the same as the call in the example: https://github.com/brentru/Adafruit_CircuitPython_SGP30/blob/master/examples/sgp30_simpletest.py#L27) as well? Naming would be: tvoc, tvoc_base, co2eq, co2eq_Base |
Yes please. I'd name them |
The CCS guide needs to be updated: https://learn.adafruit.com/adafruit-ccs811-air-quality-sensor?view=all#circuitpython-wiring-test |
@tannewt will do. |
Modified the CCS and SGP30 guides to match the naming consistencies. |
Awesome! I think this is done then. Please reopen if not. |
To avoid hijacking an unrelated thread I move this here. Currently there is mixed capitalization in the design guide concerning unified sensor driver property naming.
Consistency is usually good thing. If everything is lowercased there is no need to remember whether one should use capital letters or not. For example lux might be confusing. Is it acronym or word? Should it be
sensor.lux
orsensor.LUX
? Also when seeingsensor.TVOC
one is not really sure if it is a constant or property.I do not have strong feelings about this, but my choice would be lowercased acronyms
sensor.tvoc
andsensor.eco2
.The text was updated successfully, but these errors were encountered: