-
Notifications
You must be signed in to change notification settings - Fork 49
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
Move Auspice dep from the server code to the auspice-client customizations #673
Conversation
Removes the only reason for the server code to depend on Auspice. This function hasn't changed in Auspice in over 2 years and is unlikely to in the future. It seems to me that we're more likely to drop backwards compat with v1 first.
…for Auspice move there Related-to: <nextstrain/nextstrain.org#673>
9ddce20
to
497b42c
Compare
497b42c
to
36e511c
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.
Glad to see this! Looks good pending the CI fix.
36e511c
to
6dc47dc
Compare
…tions Avoids bringing in all of Auspice's deps into the server code. This is generally useful, but it was also specifically useful in recent prototyping to allow use of React 18 server components (as Auspice requires React 16). In any case, I think organizationally this makes more sense anyway. Related-to: <nextstrain/auspice#1661>
6dc47dc
to
3205a85
Compare
So my first fix worked in CI… but failed locally when I tested it. That's because I tested it by doing:
which failed when the Gatsby build couldn't find the I fixed it again by moving that dep into auspice-client, which works locally with the above test. As long as CI passes now, I'll merge. |
See commit messages.
Related issue(s)
nextstrain/auspice#1661
Testing