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.
feat: add log-points for NCA user input changes #1221
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
base: 1210-enhancement/replace-logger-with-console
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
feat: add log-points for NCA user input changes #1221
Changes from 13 commits
41b94035922af87ce0384ef5b7de4a4b92d91ca90b47f533b550e0bbb3785041227387dacc0c2893084b2f0b9d82a347e11cb624407a2d6eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
Inconsistent interpolation style. Line 289 (existing) uses glue-style:
log_info("Parameter selection for '{study_type}': {n_params} parameters selected.")This new line uses paste-style:
If the base branch (#1212) defines
log_info/log_debugas paste-based (no glue), then line 289 is the one that needs updating. Either way, pick one style and apply it consistently.Suggested fix — assuming paste-style is the new convention:
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.
ignoreInit = TRUEprevents firing on first render, butinput$methodis still updated programmatically during settings restore via.restore_non_filter_settings→updateSelectInput(session, "method", ...). This will log "Extrapolation method changed" when the user uploads settings — which is a restore, not a user change.The analyte, specimen, and profile observers already guard against this with
filters_initialized(). Consider applying the same pattern here:If logging during settings restore is intentional, add a comment noting that.
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.
This
log_infofires on everymanual_slopes()invalidation — including programmatic updates (settings restore, initial render). The PR description states "No logging on reactive invalidation noise — only meaningful user actions," but this observer has noignoreInit = TRUEand no guard against non-user-driven updates.Suggested fix — track whether the user triggered the change via the add/remove buttons:
Alternatively, move the
log_infointo theadd_ruleandremove_ruleobservers directly (after the table mutation), which avoids the guard entirely.