Jeremy Asuncion
Jeremy Asuncion
PR for this issue has been created and is on hold pending review: https://github.com/chanzuckerberg/napari-hub/pull/796
Checked on prod and I think a relevance sort option will always be triggered when searching @bnelson-czi
recently got some 400 errors today related to a user somehow accessing the plugins page using the template variable `[name]`: this would mean they accessed `/plugins/[name]` somehow. overall this isn't...
@liaprins-czi let me know if you want to solve this a different way, but I think making the in-page table of contents scrollable should be fine here
marking as P0 since this will trigger AWS alerts when https://github.com/chanzuckerberg/napari-hub/issues/1064 is complete
I wonder if it's possible to have mismatched API_URL between server container and frontend build, if that won't be an issue then we can probably add it at build time
Right now we proxy client side requests through [Next.js API routes](https://nextjs.org/docs/api-routes/introduction). I think this is fine, which is why I think we don't really need to provide it at build...
sounds good! wanted to create this to open up discussion in case others have more thoughts on this 🤣 👌
maybe we can use the dev endpoint instead of internal URL for dev deployments. for example: https://api.dev.napari-hub.org/dev-shared/plugins/index
@DragaDoncila by chance are you using your monitor vertically while coding or do you just somehow have a really tall monitor? this issue is reproducible if the viewport height is...