Change maxLandingPadSize type to integer #163
Draft
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
Modified maxLandingPadSize property across the application to use integer values instead of string. This includes changes in the database, entity classes, and filter classes. The update not only simplifies comparisons but should improve application performance on station queries.
|
Can we shelve this? Not saying no to it, not saying yes to it, but something we can revisit should the performance need arise. |
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.
Modified maxLandingPadSize property across the application to use integer values instead of string. This includes changes in the database, entity classes, and filter classes. The update not only simplifies comparisons but should improve application performance on station queries.