-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix(pdf-service): styling fixes after move to pdfkit #1530
Conversation
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! Minor comment for clarification but otherwise great :)
expect.any(Number), | ||
expect.any(Number), | ||
expect.any(Object), |
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'm a bit confused on what this code is actually asserting? Why do we need these here?
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.
The pdfs for abgabeArt
ausdrucken
and online
are not the same. They have slightly different content. The test is asserting that some of the relevant content is actually fed into the methods composing the pdf. The two lines you've highlighted are arguments of the list
method (x and y position). But only the first argument is relevant, hence the arbitrary expect.any(Number)
.
Quality Gate passedIssues Measures |
https://app.asana.com/0/1203259475859667/1208782862325370