-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Adds warning on reserved datanames ("all") #1416
Conversation
Unit Tests Summary 1 files 25 suites 9m 16s ⏱️ Results for commit 300b789. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 7faecfc ♻️ This comment has been updated with latest results. |
Code Coverage Summary
Diff against main
Results for commit: 300b789 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
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.
When I try with the example code at the issue about .raw_data it doesn't show a warning for .raw_data and I don't see a test for this case.
I assume it was added to check_reserved_datanames because it is what is is for, but when I run the testing apps, I see on my terminal:
[WARN] 2024-11-15 13:09:16.0411 pid:9640 token:[] teal <span>
<code>all</code>
is reserved for internal use. Please avoid using it as a dataset name.
</span>
Is this expected? I thought it would only show up on the browser?
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.
Remember to add a test for the .raw_data case. I assume that this won't affect the code on teal.gallery or other apps, but all
might be used on wild as is not a reserved word.
@llrs-roche the Thanks for catching the console issue 👍 |
I can confirm that the messages on the R console disappeared. Thanks also for simplifying some tests. I realized that there are two messages on the app about the same issue, see image below. Could this be simplified so that it only appears once or is it by design? Locally I see a new error related to renv, I haven't seen modified anything related to this, so not sure why now it is failing now: Failure (test-module_teal.R:92:13): creation process is invoked for teal.lockfile.mode = "enabled" and snapshot is copied to teal_app.lock and removed after session ended
file.exists(renv_filename) is not TRUE
`actual`: FALSE
`expected`: TRUE Let's see what happens on the GHA, if it pass I'll approve the PR to be merged |
Good eye @llrs-roche I noticed the same oddity We need to confirm if that is a bug added in the last few weeks or a feature that groups all errors together at the top. Discussion moved to: #1409 |
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.
LGTM
Pull Request
Fixes #1379
Changes description:
pluralize()
function that allows a simplification of code (removing a bunch ofif
/ifelse
statements)Special ask for reviewer