Feature Requests

This file will contain all the necessary details and we take first n lines to show as description in project cards

Add a side panel, preferably to the left of the playground screen which shows a list of all the events triggered when we flow through the diagram.

cmd+k for help

Say we are modelling a cache and using simple JS objects to do so. It'd be great to have a view where changes done to that object are show up-front in the node.

Write simple TS code to create interactive diagrams.

Currently we store the files for a project as blob and use in-memory operations to perform tasks over that blob. This works well if you are trying a few things in a playground but to do more than that, such as conducting a review of the architecture, or collaborating with team members, we need something better. Good thing is, code is at the centre of our platform, which means we can use the already mature solutions for these problems. In this case, that's Git.

I propose we integrate Architecture Review Through Pull Requests (APRs) into our development process. Given that Metz utilizes code to create architectures, this feature enables us to apply the rigor and precision of code review practices directly to design review. By leveraging APRs, we can enhance the thoroughness and effectiveness of our architectural evaluations. This approach not only streamlines the design review process, making it as familiar as code reviews, but also ensures a higher quality and consistency in our architectural decisions.

Writing all the scenarios while designing is tedious and frankly, error prone. But, because our architectures are backed by code, we can use a very familiar approach, that is, test cases. Each test case represent a path that can be taken, and that's exactly what we want for our architecture as well.