-
-
Notifications
You must be signed in to change notification settings - Fork 22
Fixes validation and case when worst flag does not exist #1543
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
averissimo
merged 9 commits into
fix-tm_abnormaliry@279-interactive_variables@main
from
fix_mods@fix-tm_abnormaliry@279-interactive_variables@main
Jun 26, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
561ea58
fixes validation
averissimo 3694ec4
chore: moves check to module
averissimo 62cb7c9
fix: tests
averissimo 74c6a77
fix: minor changes to better reflect original module
averissimo 6635aa6
[skip roxygen] [skip vbump] Roxygen Man Pages Auto Update
github-actions[bot] d351c6f
Apply suggestion from @osenan
averissimo f95fb25
[skip roxygen] [skip vbump] Roxygen Man Pages Auto Update
github-actions[bot] 408372d
docs: update document
averissimo 6115881
style: update
averissimo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@osenan non-outdated code here
Do we need this protection? I'm worried about other consequences in other modules.
It was moved to the module to prevent generic error. This is a minor change to protect against a never ending calculation of rtables
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to clarify. This line is not existing in the code right now, you are asking if it is required. IMO it is not required. I tried to create an example of this scenario to fail but I could not found a case where the app works. Before the app runs the join keys always fails If I filter and keep the parent dataset without rows. It always fails so I expect this protection to be really an edge case that it is not necessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without this it risks hanging on forever
Just remove the line and run the example, then select
N