Skip to content
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

Closed
1 of 5 tasks
thescientist13 opened this issue May 8, 2021 · 3 comments · Fixed by #80 or ContributaryCommunity/topology#21
Closed
1 of 5 tasks

some selections don't seem to be working #71

thescientist13 opened this issue May 8, 2021 · 3 comments · Fixed by #80 or ContributaryCommunity/topology#21
Assignees
Labels
0.2.0 bug Something isn't working question Further information is requested

Comments

@thescientist13
Copy link
Member

thescientist13 commented May 8, 2021

Type of Change

  • New Feature Request
  • Documentation
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

Some selection don't seem to be working anymore?

Screen Shot 2021-05-08 at 11 53 04 AM

Screen Shot 2021-05-08 at 11 56 23 AM

Screen Shot 2021-05-08 at 11 56 23 AM

Details

  1. JavaScript -> bnb
  2. JavaScript -> Gatsby
  3. JavaScript -> Project Evergreen

Screen Shot 2021-05-08 at 5 51 38 PM

@thescientist13 thescientist13 added the bug Something isn't working label May 8, 2021
@thescientist13 thescientist13 self-assigned this May 8, 2021
@thescientist13 thescientist13 added the question Further information is requested label May 9, 2021
@thescientist13
Copy link
Member Author

I think this may be a case of having different API proxies setup for different environments that just might be need to be "normalized"

  • Local: Greenwood devServer / Production
  • Deploy Preview: redirects configuration in netlify.toml
  • Production: AWS API Gateway

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

@thescientist13
Copy link
Member Author

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.

@thescientist13
Copy link
Member Author

Identified a bug with local development, raised an issue upstream @ ProjectEvergreen/greenwood#598

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.2.0 bug Something isn't working question Further information is requested
Projects
None yet
1 participant