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

feat(area): move area command creation #2322

Open
wants to merge 18 commits into
base: dev
Choose a base branch
from

Conversation

TheoPascoli
Copy link
Contributor

add a command to move an area on the map. Replace multiple UpdateConfig commands

Copy link
Contributor

@MartinBelthle MartinBelthle left a comment

Choose a reason for hiding this comment

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

We could add unit test for this command as we only have one currently.

Copy link
Contributor

@maugde maugde left a comment

Choose a reason for hiding this comment

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

It seems good to me

Copy link
Contributor

@MartinBelthle MartinBelthle left a comment

Choose a reason for hiding this comment

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

Could be nice to add a unit test on the command

antarest/study/business/area_management.py Outdated Show resolved Hide resolved
antarest/study/business/model/area_model.py Outdated Show resolved Hide resolved
Copy link
Contributor

@MartinBelthle MartinBelthle left a comment

Choose a reason for hiding this comment

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

I encountered a "bug" which was already present before your dev. When updating the color of an area inside the layer1, it also brings back its position to the layer 0 position. I don't think we should do that.

We should investigate and if we can change this, fix it and add a test inside the test_area.py file you introduced

@TheoPascoli TheoPascoli marked this pull request as draft February 6, 2025 13:33
@TheoPascoli TheoPascoli marked this pull request as ready for review February 6, 2025 13:34
@TheoPascoli
Copy link
Contributor Author

We can merge this. I will create a ticket adressing the bug that might comes from the front

@TheoPascoli TheoPascoli requested a review from a team February 6, 2025 13:36
set: t.Optional[t.List[str]] = None


# review: is this class necessary?
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it still wip ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I removed the comment because it is still used. Thanks for pointing out

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