I understand now, and I really appreciate the detailed explanation. I fully agree that this is something that should be improved.
I believe we will address this in the near future.
Thank you!
Hi Cristian,
Thank you for your kind words and for sharing your experience with ComposeSDK! We’re glad to hear it has been a boost to your productivity.
Regarding the issue you encountered, I’d like to clarify:
Are you looking for an automatic mechanism that updates the datasource TS types generated by the `sdk-cli` tool whenever there are schema changes in the Sisense instance?
> Are you looking for an automatic mechanism that updates the datasource TS types generated by the `sdk-cli` tool whenever there are schema changes in the Sisense instance?
No. I am expressing my concern that the generated schema is too lax and does not warn me when Dimensions have been removed. More specifically: I am using the schema to build a query for `useExecuteQuery` and I am specifying dimensions such as `DM.Article.SupplierName`. The problem I ran into is that I made changes to the elasticube and updated the schema using the cli and now the `SupplierName` dimension does not exist anymore, but I get no error from the typescript type checker. One can type `DM.Article.BogusDimension` and there will be no error. This could be easily solved in the SDK by dropping `[propName: string]: any;` from the type definition of `Dimension`.
I understand now, and I really appreciate the detailed explanation. I fully agree that this is something that should be improved.
I believe we will address this in the near future.
Thank you!
