-
Notifications
You must be signed in to change notification settings - Fork 12
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
Jupyter notebook does not display a html table #134
Comments
Thanks! |
@daslu So I opended bug report here: |
@RoelofWobben |
@daslu I have them already on my to do lists. scicloj/kindly-render#30 I have locally fixed this concrete issue with a workarround, so not using kindly-render when the value is dataset This is as well related to the question of "recursive table rendering". (which a dataset does not support, correct ?) |
We have "table support" marked as "yellow" in our compatibility table: But I agree, not "render at all" is a bigger problem, then "render differently" (which all other yellows mean) I am not sure, if I can/should address the not working case of "(kind/table (take 5 people-as-maps))" as "an exception in clojupyter". For the recursive rendering I rely on "kindly-render" and I don't want to "take/copy that into clojupyter". To me we need to fix the 2 above issue in kindly-render to fix "(kind/table (take 5 people-as-maps))" |
@RoelofWobben we are aware that the kindly compatibility of clojupyter is not yet 100 %. "Clay" is 100 % compatible, in fact the Noj book: https://scicloj.github.io/noj/noj_book.tablecloth_table_processing.html is rendered using Clay. (https://github.com/scicloj/clay) We are of course aiming for 100 % compatibility, and welcome all reports of differences between Clay and clojupyter. |
Thanks for these clarifying comments, @behrica. |
Hello,
IM following this page of the noj book : https://scicloj.github.io/noj/noj_book.tablecloth_table_processing.html
But as soon as I try to display the html table I do not see it on a jupyter notebook.
See this screenshot:
The text was updated successfully, but these errors were encountered: