fix limit types #186
Merged
fix limit types #186
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
catkins-miso
force-pushed
the
139-fix-limit-types
branch
3 times, most recently
from
29c2efa to
0e25b4a
Compare
catkins-miso
force-pushed
the
139-fix-limit-types
branch
from
0e25b4a to
2aac3c7
Compare
|
sorry for the noise, this should be ready now |
getorymckeag
approved these changes
Oct 11, 2024
| required: | ||
| - kV-min | ||
|
|
||
| current-with-kV: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #139
require all fields in a limit to ensure that the slim processing is unambiguous/uncomplicated by dealing with optional fields