Right now every time we want to open the telescope picker, we have to run the dbt cli.
We could make use of some kind of caching strategy to speed up the process.
We would store the state of the output, using the state of files inside the dbt project, we would redirect to the cached result when none had changed.
Even better we could attached the function responsible to generate the model state when a buffer is saved, to try to avoid cold start to a maximum.
I'm up to looking into such a thing, but do you have another view on how to reason about this thing ?
Right now every time we want to open the telescope picker, we have to run the dbt cli.
We could make use of some kind of caching strategy to speed up the process.
We would store the state of the output, using the state of files inside the dbt project, we would redirect to the cached result when none had changed.
Even better we could attached the function responsible to generate the model state when a buffer is saved, to try to avoid cold start to a maximum.
I'm up to looking into such a thing, but do you have another view on how to reason about this thing ?