Current Limitation

Currently, the tree view rendering relies on the package/components API, which lacks comprehensive information needed for the diagram. This forces the client to make multiple API calls to gather the required data, resulting in a performance bottleneck. To address this issue, we're implementing an event-driven approach that will only process and produce changes based on didChange text events.

Suggested Improvement

Implement two APIs:

1. artifacts API that produces all the artifacts for the project. This should be run initially to get the artifacts of the current package.
2. publishArtifacts API to generate only the artifacts that are relevant to the changes captured in the didChange API.

Version

No response