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
In order to add the functionality needed to add new samples, we clearly need to reimplement all of the catalog infrastructure used to render the existing samples.
That conclusion should not be too surprising - carmel is really a next generation catalog, that we started to implement in Typescript to ensure type-checking at all times. There is a plan to release carmel as just a tag editor, but in order to get even this minimal functionality in place, the current catalog has to be changed to fetch all its information from the carmel-api application.
...
The text was updated successfully, but these errors were encountered:
In order to add the functionality needed to add new samples, we clearly need to reimplement all of the catalog infrastructure used to render the existing samples.
That conclusion should not be too surprising - carmel is really a next generation catalog, that we started to implement in Typescript to ensure type-checking at all times. There is a plan to release carmel as just a tag editor, but in order to get even this minimal functionality in place, the current catalog has to be changed to fetch all its information from the carmel-api application.
...
The text was updated successfully, but these errors were encountered: