Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

Feature/592 implement heat map on the frontend #804

Open
wants to merge 182 commits into
base: master
Choose a base branch
from

Conversation

badnames
Copy link
Member

@badnames badnames commented Aug 7, 2023

Please note:
This PR is based on #684 and #684 should therefore be merged first.

This PR does not include facilities for adding map bounds or the shade layer, they will be added in a separate PR so we keep this one as simple as possible.

Special thanks to @Bushuo for helping me find an annoying bug related to axios loading binary data that prevented me from submitting this PR before friday ❤️.

Basics

  • I added a line to /doc/CHANGELOG.md
  • The PR is rebased with current master.
  • Details of what you changed are in commit messages.
  • References to issues, e.g. close #X, are in the commit messages.
  • The buildserver is happy.

Checklist

  • I have installed and I am using pre-commit hooks
  • I fully described what my PR does in the documentation
    (not in the PR description)
  • I fixed all affected documentation
  • I fixed the introduction tour
  • I wrote migrations in a way that they are compatible with already present data
  • I fixed all affected decisions
  • I added unit tests for my code
  • I added code comments, logging, and assertions as appropriate
  • I translated all strings visible to the user
  • I mentioned every code or binary not directly written or done by me in reuse syntax
  • I created left-over issues for things that are still to be done
  • Code is conforming to our Architecture
  • Code is conforming to our Guidelines
    (exceptions are documented)
  • Code is consistent to our Design Decisions

Review

  • I've tested the code
  • I've read through the whole code
  • Examples are well chosen and understandable

Moritz Schalk and others added 10 commits March 27, 2024 21:51
Co-authored-by: danielsteinkogler <[email protected]>
<!--
Check relevant points but **please do not remove entries**.
-->

## Basics

<!--
These points need to be fulfilled for every PR.
-->

- [x] I added a line to [changelog.md](/doc/changelog.md)
- [x] The PR is rebased with current master.
- [x] Details of what you changed are in commit messages.
- [x] References to issues, e.g. `close #X`, are in the commit messages
and changelog.
- [x] The buildserver is happy.

<!--
If you have any troubles fulfilling these criteria, please write about
the trouble as comment in the PR.
We will help you, but we cannot accept PRs that do not fulfill the
basics.
-->

## Checklist

<!--
For documentation fixes, spell checking, and similar none of these
points below need to be checked.
Otherwise please check these points when getting a PR done:
-->

- [ ] I have installed and I am using [pre-commit
hooks](../doc/contrib/README.md#Hooks)
- [ ] I fully described what my PR does in the documentation
- [ ] I fixed all affected documentation
- [ ] I fixed the introduction tour
- [ ] I wrote migrations in a way that they are compatible with already
present data
- [ ] I fixed all affected decisions
- [ ] I added automated tests or a [manual test
protocol](../doc/tests/manual/protocol.md)
- [ ] I added code comments, logging, and assertions as appropriate
- [ ] I translated all strings visible to the user
- [ ] I mentioned [every code or
binary](https://github.com/ElektraInitiative/PermaplanT/blob/master/.reuse/dep5)
not directly written or done by me in [reuse
syntax](https://reuse.software/)
- [ ] I created left-over issues for things that are still to be done
- [ ] Code is conforming to [our Architecture](/doc/architecture)
- [ ] Code is conforming to [our Guidelines](/doc/guidelines)
- [ ] Code is consistent to [our Design Decisions](/doc/decisions)
- [ ] Exceptions to any guidelines are documented

## Review

<!--
Reviewers can copy&check the following to their review.
Also the checklist above can be used.
But also the PR creator should check these points when getting a PR
done:
-->

- [ ] I've tested the code
- [ ] I've read through the whole code
- [ ] I've read through the whole documentation
- [ ] I've checked conformity to guidelines
Shade layer is currently broken.
@badnames
Copy link
Member Author

jenkins build please

@badnames
Copy link
Member Author

jenkins build please

2 similar comments
@badnames
Copy link
Member Author

jenkins build please

@badnames
Copy link
Member Author

jenkins build please

@badnames
Copy link
Member Author

badnames commented Apr 18, 2024

@markus2330
@horenso
@danielsteinkogler
@hatchla
@chr-schr

After yet another week of bug fixing, this branch should be ready to become our new dev branch.
Unfurtunately the pipeline seems to be broken, so I could not make sure that the project builds at the moment.

@markus2330
Copy link
Contributor

@badnames great, thank you! ❤️

@filo14 can you check out the pipeline?

@filo14
Copy link
Contributor

filo14 commented Apr 18, 2024

There are some errors regarding shadings.rs and timeline.rs in test; things like unresolved classes etc. . When I checkout the branch locally I have similar error warnings.

On another note, the pipeline fails very often at the moment, but should be a seperate problem.

@badnames
Copy link
Member Author

badnames commented Apr 18, 2024

On another note, the pipeline fails very often at the moment, but should be a seperate problem.

That was what I meant.
I tried to run it three times yesterday and it always failed because it could not connect to the database while testing migrations.

image

There are some errors regarding shadings.rs and timeline.rs in test; things like unresolved classes etc. . When I checkout the branch locally I have similar error warnings.

That is already fixed.

@badnames
Copy link
Member Author

jenkins build please

1 similar comment
@badnames
Copy link
Member Author

jenkins build please

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement Heat-Map on the Frontend
5 participants