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
@bazooka720 I've just noticed this issue, sorry for not replying sooner. When I've started developing the library, the idea was to provide a semantic layer as a library, with provided type safety. The initial API was very similar to the cube.dev format, but it has since diverged (in next-major branch), mainly because one of the main use cases (at least for us) is exposing the API to LLMs, so wherever it was possible, I've adjusted the API so the LLMs have easier time generating correct queries. So, API compatibility with cube.dev and similar tools is not one of the goals.
That being said, if you want to expose this over the API, I assume you don't care that much about the type safety as long as the final artifact has the same guarantees as the one built with the builder API. So, I'll leave this issue open, think about what would be the best way to approach it, and revisit later.
Do you have plans to make the models in YAML format? Alternatively, leverage similar to cube.dev format (or other popular) for consistency?
The text was updated successfully, but these errors were encountered: