-
Notifications
You must be signed in to change notification settings - Fork 3
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
some selections don't seem to be working #71
some selections don't seem to be working #71
Comments
I think this may be a case of having different API proxies setup for different environments that just might be need to be "normalized"
Need to make sure all environments have support for the same thing, like query strings. Should test a representative sample of projects and make sure they work across all three contexts. Somewhat related, but one of the above examples provides a message that repo has been moved. It would probably be good to have some better handling in this project with a way to report errors if possible. Made an issue for this - #78 |
So looks like for some of these cases, names have changed (Gatsby -> GatsbyJS) or moved bnb -> good first issue. Those will need to be changed in this project's topology. That said, I did identify a bug wherein Greenwood dev server does not handle URL parameters so will need to file an issue for that. |
Identified a bug with local development, raised an issue upstream @ ProjectEvergreen/greenwood#598 |
Type of Change
Summary
Some selection don't seem to be working anymore?
Details
The text was updated successfully, but these errors were encountered: