Alois Klink

> Do we throw the right errors to convey that they need to dedent it themselves? I've improved the error messages in https://github.com/mermaid-js/mermaid/pull/3859/commits/accba3f408d1f1a9a68a05fff9899e2d51627fe7 The following error is now thrown if...

> Apologies, missed this. Can you please sync? Synced! Thanks for the reminder. > What are your thoughts on exposing the detend functionality as a function, so others could utilize...

> After discussion, we've decided to split the zenUML code into a separate repo so that it's easier to maintain. I agree! The current Mermaid source-code is only 575 files...

:+1: I wanted to make an issue, but it didn't match any of the current GitHub Issue templates in https://github.com/mermaid-js/mermaid/issues/new/choose, since it wasn't a bug report, or diagram/syntax/theme proposal. @sidharthv96,...

Looks like the Mermaid repo has signed up for the **Merge queue** beta!! Thanks to whoever added this! See https://github.com/mermaid-js/mermaid/queue/develop I'm going to close this issue, but we can comment...

Do we know when v10 is expected? ~On my side, I have a WIP that slightly updates the types of `MermaidConfig`~ Edit: added in PR #4112 **without any breaking changes**,...

> Can you make a PR with your changes? My PR is at #4112. However, I made that PR **without any breaking changes**, so it can wait until a `v10.0.1`....

I have a pending PR that will change the `MermaidConfig` to be defined in a single-file[^1] using [JSONSchema](https://json-schema.org/): https://github.com/mermaid-js/mermaid/pull/4112 (it's got a bunch of merge conflicts that I don't want...

> @aloisklink, now that https://github.com/mermaid-js/mermaid/pull/4112 is merged, should we create separate issues for the 2 breaking changes mentioned? I think, after talking to @Yokozuna59, we can do be both of...

### Git force push changes I've `git rebase`-d onto `develop` to fix merge conflicts (and some PR comments). You can use the following command to view the changes (GitHub's UI...