front: implement new scenario header #11627
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kmer2016
force-pushed
the
cnh/front/new-scenario-view-header
branch
2 times, most recently
from
0b4c140 to
939f8ee
Compare
kmer2016
force-pushed
the
cnh/front/new-scenario-view-header
branch
2 times, most recently
from
3ce0f84 to
0328673
Compare
SharglutDev
reviewed
May 6, 2025
Contributor
SharglutDev
left a comment
SharglutDev
left a comment
There was a problem hiding this comment.
Thank you for the PR, nice to see the first stone of the new UI :)
front/src/applications/operationalStudies/v2/components/ScenarioHeader.tsx
Show resolved
Hide resolved
front/src/applications/operationalStudies/v2/components/ScenarioHeader.tsx
Outdated
Show resolved
Hide resolved
front/src/applications/operationalStudies/v2/components/ScenarioHeader.tsx
Outdated
Show resolved
Hide resolved
front/src/applications/operationalStudies/v2/components/ScenarioHeader.tsx
Show resolved
Hide resolved
front/src/styles/scss/applications/operationalStudies/_scenarioV2.scss
Outdated
Show resolved
Hide resolved
front/src/styles/scss/applications/operationalStudies/_scenarioV2.scss
Outdated
Show resolved
Hide resolved
front/src/styles/scss/applications/operationalStudies/_scenarioV2.scss
Outdated
Show resolved
Hide resolved
front/src/styles/scss/applications/operationalStudies/_scenarioV2.scss
Outdated
Show resolved
Hide resolved
front/src/styles/scss/applications/operationalStudies/_scenarioV2.scss
Outdated
Show resolved
Hide resolved
SharglutDev
approved these changes
May 7, 2025
Contributor
SharglutDev
left a comment
SharglutDev
left a comment
There was a problem hiding this comment.
Lgtm and tested, thanks ! (you can close the last comment when indentation is fixed)
Contributor
|
If I'm not mistaken, the plan was to integrate these new interfaces directly inside the current one and not used a secondary path url ? |
Contributor
Author
Yes, that’s the long-term goal. But first, we’ll build the structure of the UI on the second URL. Once the structure is ready and we need to integrate the components from the current version, we’ll do that directly on the current URL. |
kmer2016
force-pushed
the
cnh/front/new-scenario-view-header
branch
2 times, most recently
from
55b576c to
385c46d
Compare
Signed-off-by: nncluzu <ngamenichaka@yahoo.fr>
kmer2016
force-pushed
the
cnh/front/new-scenario-view-header
branch
from
385c46d to
81f42ad
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement the header for the new Scenario view.see mock-up.
This PR includes only the UI; it adds no interactions.