#Is there a known issue with daggerverse
1 messages ยท Page 1 of 1 (latest)
are you using firefox?
๐
Haha - no worries
Can you send me a screenshot of what you see?
I know its different between firefox and chrome.
Markdown parsing is also not supported officially
Here's chrome v Firefox -- at least new lines are there in Chrome
i wonder why it doesnt respect the first list to be 2 seperate lines
its just python """ """ which has \n in it i thought
This feels new to me
Your chrome one is "better" but still has this sneaky breaking bit
Yeah I see that now.
I want to file an issue, @inner turret should we put these in dagger/dagger?
yes please, use dgvs: or daggerverse: in title
this should also be considered non- markdown right? "plain text support with new lines" is what this is essentially?
Yes. Currently Markdown is not supported. I'll look at the routine that scrubs the plaintext and see if the issue is there.
filed this: https://github.com/dagger/dagger/issues/7541
thank you!
--version string idl2-schemata --file file:path in the daggerverse
but... in the CLI tool locally
idl-2-schemata Convert an Avro IDL file to Avro schema files in the provided directory
ohh, could that be to do with like a version of dagger interpreting the module?
I think this is also a bug ๐ฆ
im on ๐ฅ with the reports
Yes, I think in the CLI we treat the number 2 as a place to put a - like a camel-case transition point, but that is not being rendered in the auto-generated examples in the Daggerverse. The CLI should be authoritative.
cc @short pine
Got a quick fix, I think