-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
chore(gatsby): disable loki stuff without dropping it #23646
Conversation
09bb003
to
e1293bf
Compare
8f0e8b6
to
82a446e
Compare
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.
Phew
Want to comment out the switch cases in packages/gatsby/src/db/nodes.js as well? You mentioned that you'd follow up to clean up, so can happen then
Yeah we'll drop the whole thing at once next sprint. This is only commenting out the pieces that change things based on the flag. |
Added message to warn against usage. |
Co-authored-by: Sidhartha Chatterjee <[email protected]>
Published in [email protected] |
This PR prevents Loki from being used anymore within Gatsby.
The PR is only disabling Loki specific code paths, not removing them. That'll be a followup commit that's much more invasive than this one.
Basically, after this commit,
GATSBY_DB_NODES=loki
shouldn't change anything anymore in terms of how Gatsby works.Also tried to disable circle ci checks for loki.