Niklas Mollenhauer

Now fixed in core library: https://github.com/nikeee/dot-language-support/commit/c724aac41053a05dc824b78215c545c4b24fcab0 Porting this over to edotor.

This is just for the auto completion, though. It seems that they were added in a newer version of GraphViz. We're using a divverent rendering library than the site you...

Cool idea! I think with the current implementation, this would not be straight-forward. The rendered graph is an SVG generated by [viz.js](https://github.com/mdaines/viz.js), which is the real GraphViz compiled for the...

It seems that nodes get IDs in the order they are referenced in (`node1` for the first node etc). Maybe we can leaverage this to do some "go to definition"...

@hpcc-js/wasm seems like a good alternative: https://www.npmjs.com/package/@hpcc-js/wasm

We should investigate whether this is still a problem in firefox.

The error occurs when doing a [production build](https://next.angular.io/guide/aot-compiler) with [fullTemplateTypeCheck](https://next.angular.io/guide/angular-compiler-options) enabled.

You are right. I had this error when compiling: ``` Argument of type 'readonly IOption[]' is not assignable to parameter of type 'IOption[]'. The type 'readonly IOption[]' is 'readonly' and...

> It could be a breaking change if compilation fails for those users who currently provide a list of options that is not readonly. AFAIK it shouldn't. The `readonly` modifier...

I tried implementing this using a generic approach, allowing only string and number (can be expanded to boolean as well): https://github.com/basvandenberg/ng-select/compare/1.0.3...nikeee:feature/allow-string-and-number?expand=1 It should not be a breaking change, as the...