-
Notifications
You must be signed in to change notification settings - Fork 46
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
front: manchette: display waypoints added with map click #8698
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #8698 +/- ##
============================================
- Coverage 37.03% 37.00% -0.04%
Complexity 2208 2208
============================================
Files 1255 1255
Lines 113915 113969 +54
Branches 3188 3188
============================================
- Hits 42192 42176 -16
- Misses 69828 69898 +70
Partials 1895 1895
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
3ca0d01
to
e952eb8
Compare
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
34ee92d
to
48f12d2
Compare
front/src/modules/simulationResult/components/SpaceTimeChart/SpaceTimeChartHeader.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With that extraneous file removed, LGTM! Thanks for the fix!
71808d1
to
6fe48ce
Compare
Yep my bad -_- |
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Show resolved
Hide resolved
.../modules/simulationResult/components/SpaceTimeChart/useGetProjectedTrainOperationalPoints.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !
b745e1b
to
b41838d
Compare
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
In general I prefer to avoid `as` type assertions as much as possible, because it makes the compiler ignore any type mismatch. The non-null assertion operator `!` is a bit better: if the types don't match, the compiler will error out. Use it in a bunch of places. See #8698 (comment)
fix #8174