update params

yeah its obsolete. This is an old branch that recently got synced with latest staging. It looks like the CR doesn't recognize the correct changes from staging. There should only be 1 file change ( conductivity sensors ).

removed

Remove this extra line

I added the unique decorator back, except for the few that have aliases

Renamed, also flagged for future type change.

"No one should interact with it or be aware of it's existence, so the name shouldn't matter."

• it matters to those who read the code in inconsistent intervals ( like those who participate in code review or teaching ).

"As we only have 2 version in test at the same time."

• Currently. By summer, i'd expect dialin to be considering 1.0's, 1.9s, and 2.0s/DVTs.

We have the choice to handle the redesign effort then or now.


Edit:
Follow up comment.

Looking at the other files. Users of dialin will not be aware of existence, but developers of dialin will as it impacts the behavior of overrides like temp & pressure.

yes. that's the design consideration. Are we okay with our unit tests no longer checking for duplicate values? ( they will currently pass as i remember they expect an exception due to the unique keyword to fail. These will not trigger an exception ).

I am not sure I can assign unique to the dynamic enums. Also with unique you can't add aliases and some(for example: temperature) overrides use the aliases to determine which msg id to call and how much to shift value for it.
Making an alias is more dynamic and not needing separate variables to be maintained for this.

Enum content of Beta 1.0 and Beta 1.9 is different. The new sensors messing up the order for the old HW's override and broadcast data allocation.
Making it dynamic makes it that when the beta test config is called the enums are switching content to reflect that.

Reasons:

• No one should interact with it or be aware of it's existence, so the name shouldn't matter.
• As we only have 2 version in test at the same time, I am making an internal variable name that I don't need to rename every 3 months or so.
  Needing to make a review smaller with editing less thing makes it faster to be completed...

In case a situation arrives when we will test more version at the same time Alpha, Beta, Beta 1.9, it will require a redesign on the part of enum generation too.

previously we had the unique keyword above our classes as a developer sanity check to ensure the dev didnt duplicate values in the dict since we dont auto generate this defs.

if i remember correctly, unique is checked when the enum class is imported. We test it our unit tests, both test_constructors and test_imports.

The reason we currently would want to keep unique is because the DialinEnum class has the method has_value(). Without knowing the current usage of this function from our users, it will impact users expected behavior.

My question to you: Should we continue to test and check how the defs for duplicates?

This should be renamed to be more concise and allow flexibility as more HW revisions come. What is next gen? All BETAs? BETA 1.9? Beta 2.0? DVT?

What is the intention of making our defs dynamic and a class object rather keeping it a class?