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.

Sign up for GitHub

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

Jump to bottom

Re-route requests of /fe/{route} to /{route} where possible #92

Closed
jpwahle opened this issue Aug 18, 2022 · 0 comments
Closed

Re-route requests of /fe/{route} to /{route} where possible #92

jpwahle opened this issue Aug 18, 2022 · 0 comments
Labels
perf Pull Request: Performance increases refactoring Pull Request: Refactoring code without logic change

Comments

@jpwahle
Copy link
Owner

jpwahle commented Aug 18, 2022

Is your feature request related to a problem? Please describe.
Instead of using custom queries, we can directly use the express-restify-mongoose after jpwahle/cs-insights-backend#90 to query the backend which will be faster.

Describe the solution you'd like
All queries that were sent to /fe/papers should be adjusted to be sent to /papers
@jpwahle jpwahle added perf Pull Request: Performance increases refactoring Pull Request: Refactoring code without logic change labels Aug 18, 2022
@jpwahle jpwahle changed the title Re-route requests of /fe/papers to /papers Re-route requests of /fe/{route} to /{route} where possible Aug 19, 2022
@jpwahle jpwahle closed this as completed Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
perf Pull Request: Performance increases refactoring Pull Request: Refactoring code without logic change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jpwahle