Skip to content
  • Place to introduce & feedback about this space

    4 Topics
    12 Posts
    D

    Hi all! 👋
    My name is Mateusz, and I’m a Software Developer with over 6 years of experience working in data visualization and diagramming at Synergy Codes.
    Feel free to reach out if you have questions, need advice, or want to collaborate. 😁

  • Products & Projects related with data vis

    4 Topics
    9 Posts
    PMarcinP

    Source Code Access for Non-Commercial Evaluation

    We understand how important it is to thoroughly evaluate a solution before making a decision. That’s why we offer access to the Workflow Builder source code for internal, non-commercial evaluation purposes.

    How does it work?

    Contact us via our form (https://www.workflowbuilder.io/contact) and we’ll provide you with access to the source code and documentation.

    You can review, test, and integrate Workflow Builder within your own environment strictly for internal assessment—not for any commercial or production use.

    This evaluation license allows you to analyze the architecture, quality, and security of our product before making a purchase decision.

    If you have any questions or want to begin the evaluation process, please reach out to us!

  • Discousion and tech hub

    2 Topics
    2 Posts
    lukasz.jazwaL

    Changing a node’s dimensions sounds simple. But doing it consistently in React Flow isn’t so straightforward.

    When you look at the Node type, you’ll notice width and height attributes. It might seem like you can just update those. But according to the React Flow docs, those values are read-only. The same goes for measured: { width: number; height: number }.

    So how do you actually change a node’s dimensions?

    The React Flow team recommends using CSS. From the docs:

    “You shouldn’t try to set the width or height of a node directly. It is calculated internally by React Flow and used when rendering the node in the viewport. To control a node’s size you should use the style or className props to apply CSS styles instead.”

    That usually works. But there’s a catch.

    If you want a consistent way to both set and get a node’s dimensions, relying on the style prop might not be enough. Why? Because of the NodeResizer component.

    NodeResizer lets users resize nodes manually using UI handles. But when they do, React Flow doesn't update the style prop. Instead, it directly modifies the width and height attributes using internal state changes.

    If you look at how NodeResizer works under the hood, you’ll see that React Flow uses a NodeDimensionChange to update the node’s size.

    So how can you trigger that same kind of change programmatically using only official React Flow methods?

    Use applyNodeChanges from the React Flow API:

    const customDimensionsChange: NodeDimensionChange = { id: 'node-1', type: 'dimensions', dimensions: { width: 300, height: 200 }, setAttributes: true, }; setNodes((nodes) => applyNodeChanges([customDimensionsChange], nodes));

    This updates the width and height attributes properly. It’s the most consistent way to change node dimensions programatically in React Flow.

  • Discousion and Tech Hub

    14 Topics
    15 Posts
    B

    Following https://github.com/DataVisHub/gojs-course/blob/main/lessons/lesson-0-project-setup-and-intro.md
    It is not explained that I need to download the files from https://github.com/DataVisHub/gojs-course/ and execute

    npm run start

    from the top level folder so that the package.json file is present.
    Otherwise, the failure occurs:

    c:\>npm run start npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent
  • Lets talk about ML (AI)

    1 Topics
    1 Posts
    PMarcinP

    Based on interviews and a survey of diagrammatic experts - we have prepared a report.
    Direct link here.
    If you have any suggestions or questions - please write boldly

    de0f65a8-dcb8-4940-8e4f-f5cd0c8f39a6-image.png