search

awslabs / aws-api-gateway-developer-portal

A Serverless Developer Portal for easily publishing and cataloging APIs
Apache License 2.0
928 stars 400 forks source link

Left menu items don't react on click #376

Closed mseest closed 4 years ago

mseest commented 4 years ago

I have deployed the developer portal and added a few APIs. Though the left menu items don't react on click and change content in the main view.

image
amichot commented 4 years ago

I am having the same issue

ghost commented 4 years ago

Try replicating this on the staging branch - that should contain a fix for this. We've moved our most recent development work there, and we plan to merge that back to master once it's ready.

amichot commented 4 years ago

@amazon-meaisiah I'm having the same issue with the staging branch.

AnjaneyalnDatla commented 4 years ago

Facing the same issue using the github code.It works normally using Serverless Application Repo. Do the two have the same code?

ghost commented 4 years ago

@AnjaneyalnDatla master is not currently in sync with SAR and contains several subsequent commits. Our active work is currently on the staging branch, with plans to eventually merge it to master, but it was created after initially making some commits to master itself.

If you want stability while still using what's in the repo, my recommendation for now is to use the latest release.

AnjaneyalnDatla commented 4 years ago

Thanks @amazon-meaisiah . I tried the version you had suggested(V3.0.2) and seems like its using nodejs8.10 which isn't supported anymore, bumped the version to nodejs12 to see if that works but no luck. StaticAssetUploader function is failing - Custom Resource failed to stabilize in expected time

We are currently constrained in our ability to use SAR(we need to provide mandatory tags).So kind of stuck with SAM deployment.Can you point me to the branch version/tag which SAR is currently using. Thanks in advance

ghost commented 4 years ago

My mistake - try this commit. That is the version SAR is currently using, and that updates all the Node 8 references to Node 12 in a maintenance release. Does that help?

ghost commented 4 years ago

Should be fixed in v4.0.0, as I was able to reproduce it and then fixed it.