Hi #Angular! Just released ngx-vflow@1.12 with canvas-based virtualization - enabling smooth flows with many thousands of nodes, while keeping full HTML/SVG flexibility. Tech details: Repo:

Excited to share that in the next release, ngx-vflow will support seamless virtualization for apps with thousands of nodes!. Hit a ⭐️ to stay updated!

Hi #Angular!. I released ngx-vflow@1.10 with support for the curve factory and a stress test demo. Repo:

I'll make ngx-vflow dependency-free this year. The only thing I currently rely on now is d3.js. While it's a great library, I don't really like its API, and it adds some side effects that I have to deal with.

added edge label parsing & playing around with animated editing. I'll release this tool soon because it will be a great showcase of ngx-vflow features. Also considering extending the Mermaid format to go full custom, maybe by somehow passing components into Mermaid nodes

By the way, the Mermaid parser is written from scratch, because why not?.

I was a bit tired of pushing features to vflow, so decided actually build something on top of my library. Now working on a Mermaid editor/viewer that combines the elegance of Mermaid syntax with the rendering power of ngx-vflow

Hi #Angular! I released ngx-vflow@1.8 with improvements to the subflows API. It's now possible to conveniently attach and detach nodes from subflows.

RT @DanielGlejzner: Job ad: “Need React dev with 10 yrs exp!”. Dev: “10 yrs in Vue; can master React’s specifics quickly - core concepts ar….

Hi #Angular! I released ngx-vflow@1.7 with SVG nodes support. Also, this release includes the following improvements:.- Support for multiple node toolbars (thanks to a contribution from a community member).- Resizing now snaps to the passed grid.

I think it's better to teach people using the new Angular features. In this case, it should be the input signal, as decorator inputs may get deprecated in the near future.

Wow, @denwaya34 wrote a great article about ngx-vflow! It covers the basics of quickly drawing a simple flow using the default UI. (Sadly, I don't speak Japanese, but Chrome Translate helped me).

Sometimes it's even impossible to fix a Safari bug without rewriting everything.

I would do this:. - provide a service with a subject at the parent component level.- create an outputFromObservable(service.subject$) in the parent component.- inject this service into a deeply nested child component, next() the subject there.

Hi #Angular! Pushed a small release of ngx-vflow@1.6 with:. - ng-template context type improvements (context is no longer any!).- Some edge API changes, described in more detail on Reddit.

Today I learned that Angular allows typing the context of ng-template by ngTemplateContextGuard. So, there will be less 'any' in the next release of ngx-vflow!.

Hi #Angular! I released ngx-vflow@1.5 with the following edge improvements:. - edge reconnection feature.- increased clickable area for edges. ⭐️ As always, kindly ask you to give it a star, it greatly motivates me to keep adding new features!.

Hi #Angular! The edge reconnection feature is coming to ngx-vflow. The API will be dead simple:.1. Watch for the onReconnect event. 2. Remove the old edge and create a new one. 2. Feed the new state back into the library. ⭐️star it to stay updated:

The perfect issue.

Hi #Angular! After two months of feature freeze, I'm continuing to add new quality-of-life improvements to ngx-vflow. In 1.2 I added:. - Snap to grid.- Text edge labels (previously, required an ng-template, even for simple labels).