Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
align the indent or remove blank space before =

align the indent or remove blank space before =

remove blank space before =

remove blank space before =

Put this into a dataclass folder under common, so we start structuring it.

Put this into a dataclass folder under common, so we start structuring it.

Not in use, don't need to add

Not in use, don't need to add

2 empty lines please

2 empty lines please

2 lines between functions please

2 lines between functions please

remove empty line

remove empty line

remove 3rd empty line

remove 3rd empty line

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Rename to CanChannels

Fix it, it's CanChannels, not DenaliChannels

Fix it, it's CanChannels, not DenaliChannels

LEAHI-DIALIN-LDT-4612_Dialysate Composition (Dry Bicarbonate) - FW Iteration - 4/1:
LEAHI-DIALIN-LDT-4612_Dialysate Composition (Dry Bicarbonate) - FW Iteration - 4/1:
LEAHI-DIALIN-LDT-4484_[Dialin] Create Dry Self Test module in dialin
LEAHI-DIALIN-LDT-4484_[Dialin] Create Dry Self Test module in dialin
references to Denali has been removed

references to Denali has been removed

Shouldn't we use Leahi instead of Denali?

Shouldn't we use Leahi instead of Denali?

LEAHI-DIALIN-LDT-3904_[OpMode] The operation mode broadcasts does not return the 3rd and 4th level modes
LEAHI-DIALIN-LDT-3904_[OpMode] The operation mode broadcasts does not return the 3rd and 4th level modes
We agreed to change back the enums into the static variation. Why would that cover a class that has been implemented to mask the enums from direct access, so if they need to be changed to dynamic o...

We agreed to change back the enums into the static variation.
Why would that cover a class that has been implemented to mask the enums from direct access, so if they need to be changed to dynamic or renamed or anything, the other repositories that are using them through this class won't be affected or need any update.

Did we not decide to revert all the changes back and the redesign the whole concept again?

Did we not decide to revert all the changes back and the redesign the whole concept again?