You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User POV:
When I work with supply chains (and deliveries) I struggle to ensure :
I am matching inputs to the correct outputs
My syntax is correct
Know what my options for syntax are.
Evaluate the correctness of my supply chain without pushing the changes to a cluster.
Doc Author/support POV:
Explaining examples of supply chains is difficult without a way to visualize the shape of the supply chain and the dependencies involved.
This work is done enough to consider the spike complete. I need to add/update the 'roadmap' in the editors readme and close this issue.
I think it's worth sharing some learnings
the yaml library I am using is great, it lets me do a significant amount of lexicial analasys/ast work cheaply.
I'm not using a worker, and I'm not backing things with a language server. The worker is not necessary with the current load, but perhaps it will be when parsing multiple files at once. A language server would be much more reusable (in other editors) but is far from necessary for this one editor.
To formalize this editor as something well managed, well written, tested and CI/CDed would require a dedicated person (or pair) for a significant time. I'm thinking 4 weeks before being able to slow down and pick up other work.
Description of problem
User POV:
When I work with supply chains (and deliveries) I struggle to ensure :
Doc Author/support POV:
Explaining examples of supply chains is difficult without a way to visualize the shape of the supply chain and the dependencies involved.
Proposed solution
Introduce a live playground like ytts
I've already demonstrated a rudimentary live visualizer to the maintainers using mermaid
I propose a static web app built using
Additional Context
Happy to treat this work as a spike and publish the editor as a blog post to gather feedback while not implying ongoing support.
Spike Targets:
Implied work
Big list of awesome
The text was updated successfully, but these errors were encountered: