Allow Explicit 0 Mobility#607
Merged
Merged
Conversation
TimothyWillard
added
bug
pearsonca
approved these changes
Aug 21, 2025
Contributor
There was a problem hiding this comment.
+1 re switch to _... for internal methods.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Describe your changes.
Prior to #549 providing an explicit mobility of 0 was allowed, this reallows this previous behaivor. Minor change to the
MobilityFileRowpydantic model was required and then adjust ments to the unit tests. Should address #605.Does this pull request make any user interface changes? If so please describe.
The user interface changes are explicit mobility of 0 is now allowed.
What does your pull request address? Tag relevant issues.
This pull request addresses #605.