Skip to content
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

Warn instead of error when duplicate binding IDs are found in non-devmode #4019

Merged
merged 8 commits into from
Mar 29, 2024

Conversation

cpsievert
Copy link
Collaborator

@cpsievert cpsievert commented Mar 29, 2024

Closes #4016

Also, while looking through the code, I noticed there was a call to ShinyClientError() to notify about an id of "". This code actually isn't reachable, since when id is falsy, bindInputs()/bindOutputs() both exit early before calling addBinding(). Also, actually throwing a ShinyClientError() in that case would likely be problematic for similar reasons, so 298d8bf simply removes it.

@cpsievert cpsievert requested review from wch and nstrayer March 29, 2024 15:21
srcts/src/shiny/bind.ts Outdated Show resolved Hide resolved
@cpsievert cpsievert merged commit edd1db7 into main Mar 29, 2024
12 checks passed
@cpsievert cpsievert deleted the duplicate-id-warn-not-error branch March 29, 2024 18:51
@github-actions github-actions bot restored the duplicate-id-warn-not-error branch March 29, 2024 18:55
@cpsievert cpsievert deleted the duplicate-id-warn-not-error branch March 29, 2024 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

After upgrading to Shiny 1.8.1 from 1.8.0, no data is visible on my shiny APP
3 participants