Skip to content

Merge next br changes in#183

Open
metasoarous wants to merge 59 commits intomasterfrom
next
Open

Merge next br changes in#183
metasoarous wants to merge 59 commits intomasterfrom
next

Conversation

@metasoarous
Copy link
Owner

No description provided.

There was a bug where on the first evaluation, the path would have a / attached to the end, leading to a stackoverlow in compile; these should be caught better somehow...
at some point, the connection established message from client stopped working; not sure why. So moved to using a watch on the connected-uids atom, which is more reliable and doesn't involve a wait on the client side to ensure there's a connection
this is necessary for newly connected tabs to get all of the results
If a block is only separated by a single newline from a code comment which follows it (assuming not a md-comment), then include it as part of the block. This means that if you want code-comments to be considered the start of the next block, you need to add a blank line, as you would in markdown.
originally, was just inlining in the head of the document from resources, and I don't want to have to track all those files in git
metasoarous and others added 29 commits November 22, 2021 00:45
…ependencies as metadata annotations

this provides an escape hatch in cases where oz isn't picking up on this information analytically
this may be creating more connections than we want, meaning more data being sent over than needed
added styling-options doc
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.

1 participant