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.

Sign up for GitHub

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

Jump to bottom

Custom inspectors #51

Open
mbostock opened this issue Oct 23, 2023 · 2 comments
Open

Custom inspectors #51

mbostock opened this issue Oct 23, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@mbostock
Copy link
Member

mbostock commented Oct 23, 2023 •
edited

Symbol.for("observablehq.display")? Ref. https://docs.deno.com/runtime/manual/tools/jupyter#rich-content-output, but in our case it should return an HTML element/node for insertion, rather than a string, since we’re running in the client and we don’t need serializable values.
@mbostock mbostock added the enhancement New feature or request label Oct 23, 2023
@mbostock mbostock mentioned this issue Oct 23, 2023
Closed
@Fil Fil mentioned this issue Nov 1, 2023
Closed
@mbostock mbostock added this to the Future milestone Nov 13, 2023
@Fil Fil removed their assignment Nov 27, 2023
@Fil
Copy link
Contributor

Fil commented Mar 23, 2024

related to #23 #1120

@mbostock
Copy link
Member Author

For precedent there is also Symbol.for("nodejs.util.inspect.custom").

Another approach would be to register custom inspectors in the config.

@mbostock mbostock removed this from the Future milestone Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Symbol.for("observablehq.display") observablehq/framework
2 participants
@Fil @mbostock