Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding new samples #11

Open
adriatic opened this issue Apr 14, 2017 · 0 comments
Open

adding new samples #11

adriatic opened this issue Apr 14, 2017 · 0 comments

Comments

@adriatic
Copy link
Member

adriatic commented Apr 14, 2017

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.
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant