-
Notifications
You must be signed in to change notification settings - Fork 12
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
Switch to new relations handling (on the end client) #49
Comments
Getting relations should actually be model specific. The current flow of getting all relations at server start-up will have to be replaced because each model could have its own import chain. Heiko for internal details. I think that it will just be a two-stroke start-up on the end client instead of the initial server start-up. |
Probably be part of integrating the landing page with the main editor. |
… and response; another kick down the road for #49
@hdietze Are we still considering having the per-model relations call, or are we good enough with the starting meta call? It's far enough back I'm a little unsure how we stand now... |
Division of responsibilities between minerva and golr doesn't seem clear to me. on the one hand, golr is the general source of things in the world, is used for autocomplete for classes. on the other minerva has the semantics which will likely be required for #165 For the 2015-08 push it probably doesn't matter, all the models import go-plus which imports ro |
Okay, talking to @hdietze, this is a bit of an historical artifact that has since been changed (we are no longer going to have per-model import chains). The change in bootstrapping was done in June, but I'll close it here as we have the final clarification. |
Currently using /getRelations in bootstrap, need to switch to the new handler.
Talk to Heiko if you forget (again).
The text was updated successfully, but these errors were encountered: