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

Expose warnings #1192

Open
tophtucker opened this issue Dec 19, 2022 · 0 comments
Open

Expose warnings #1192

tophtucker opened this issue Dec 19, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@tophtucker
Copy link
Contributor

tophtucker commented Dec 19, 2022

Currently, ⚠️ warnings are just sent to console.warn. It'd be great if they were also exposed programmatically, so other code (like Observable itself) can consume them.

Possible approaches:

  • as a property on the DOM node, like plot.scales
  • as an onWarn callback
  • …? add your own!

It'd be great if the warning came with information about where it originated, as if we could place an error caret at the spot in the configuration object where you should look: somewhere in the nth mark, in the x scale, etc.

Related links (mostly a note to self):

@tophtucker tophtucker added the enhancement New feature or request label Dec 19, 2022
@tophtucker tophtucker changed the title Expose warnings as property on DOM node Expose warnings Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant