-
Notifications
You must be signed in to change notification settings - Fork 530
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
Make changes to allow for /api/quality-metrics to work #2641
Conversation
Signed-off-by: cs-308-2023 <[email protected]>
@yurishkuro Some tests are failing. I have to make changes in the .test.js files |
lgtm. Is it correct that this is a breaking change (different data shape is expected)? Please document it in the description. |
can you get the CI to green? Both linter and unit tests are failing. |
I didn't understand. Can you elaborate it a bit? What data shape is actually expected? |
You are now parsing data in a different shape than before (the "data" sub-structure in json) |
yes |
Signed-off-by: cs-308-2023 <[email protected]>
Signed-off-by: cs-308-2023 <[email protected]>
370cf81
to
adefd46
Compare
Signed-off-by: cs-308-2023 <[email protected]>
adefd46
to
e757854
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2641 +/- ##
=======================================
Coverage 96.62% 96.62%
=======================================
Files 256 256
Lines 7732 7733 +1
Branches 2018 2018
=======================================
+ Hits 7471 7472 +1
Misses 261 261 ☔ View full report in Codecov by Sentry. |
packages/jaeger-ui/src/components/QualityMetrics/__snapshots__/index.test.js.snap
Outdated
Show resolved
Hide resolved
Signed-off-by: cs-308-2023 <[email protected]>
Signed-off-by: cs-308-2023 <[email protected]>
d456f23
to
31a9d39
Compare
Added in the description of the PR |
## Which problem is this PR solving? - Resolves #6607 - Related to jaegertracing/jaeger-ui#2640 - Related to the PR: jaegertracing/jaeger-ui#2641 ## Description of the changes - ## How was this change tested? - ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `npm run lint` and `npm run test` --------- Signed-off-by: cs-308-2023 <[email protected]>
@@ -92,9 +92,10 @@ export class UnconnectedQualityMetrics extends React.PureComponent<TProps, TStat | |||
this.setState({ loading: true }); | |||
|
|||
JaegerAPI.fetchQualityMetrics(service, lookback) | |||
.then((qualityMetrics: TQualityMetrics) => { | |||
this.setState({ qualityMetrics, loading: false }); | |||
.then((qualityMetrics: { data: TQualityMetrics }) => { |
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.
I don't understand why we need to be making a breaking change to the data format? The current code does not expect data:
element. The backend code does not require it either.
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
## Which problem is this PR solving? - Follow up to #6608 - Resolves #6607 ## Description of the changes - Remove intermediate `data:` element from the response - Match response to what the UI expects - Fix unit test that wasn't testing the output ## How was this change tested? - unit tests - manual test with jaegertracing/jaeger-ui#2641 --------- Signed-off-by: Yuri Shkuro <[email protected]>
Which problem is this PR solving?
Description of the changes
How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:npm run lint
andnpm run test