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

154 compute vehicle data all at once #168

Merged
merged 5 commits into from
Sep 15, 2023

Conversation

Kebslock
Copy link
Contributor

Seperated logic and database queries in vehicle service (see #154). Sadly this did not produce the desired result as it decreased the route PUT /api/vehicles/app only a little bit. More profiling on this needs to be done.

One more note on these weird looking TODOs above every null check: This will be removed in near future (probably another PR) after #163 gets merged.

@Kebslock Kebslock self-assigned this Sep 14, 2023
Copy link
Contributor

@NicoBiernat NicoBiernat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your refactor of the vehicle service and track service looks good. I suggest that we merge it to development and then pull it into #163 to complete the error handling. Then we proceed with profiling and optimizing.

One thing that we might have to think about is whether some failed calculation in e.g. getVehicleData should let the whole request fail or if we might send partial responses with just the failed computed field missing.

Since you changed something in the routes, we will probably have some merge conflicts, but we'll handle them in #163.

Please use a linter to find unused imports and other easy to fix issues in the future.

@Kebslock Kebslock merged commit b64f95d into development Sep 15, 2023
@Kebslock Kebslock deleted the 154-compute-vehicle-data-all-at-once branch September 15, 2023 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants