-
Notifications
You must be signed in to change notification settings - Fork 77
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
Migrate FixieCorpus to the new (beta) corpus API. #246
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I vote for simplicity and just cutting over to the new API. |
Thanks for the comments - PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
74ce814
to
8f92ec3
Compare
Co-authored-by: Nick Heiner <NickHeiner@users.noreply.github.com>
…mdw/new-corpus-api
The new corpus service is currently only deployed on beta.fixie.ai, however, it should be more reliable and useful than the existing app.fixie.ai API. Hence this PR updates AI.JSX's
FixieCorpus
component to use the new API surface. I've also added a little demo program for the component.If we want to retain support for the old API, I'm happy to rename this component to something like
FixieCorpusNew
or add a flag or something to use the new API instead - feedback welcome!