-
Notifications
You must be signed in to change notification settings - Fork 0
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
mrc-5953 vitest pt 2 #220
mrc-5953 vitest pt 2 #220
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.
Just a couple of questions!
@@ -276,7 +275,7 @@ describe("RunPlot", () => { | |||
fadePlot: false, | |||
graphIndex: 0, | |||
graphConfig | |||
}, | |||
} as any, |
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.
Why do you need these as any
s - is this not providing all the props the RunPlot expects? I suppose could spread an empty props object here if so, but probably not worth it!
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.
linkedXAxis
was the issue in this one! yh just thought it wasnt worth it to add it cos we dont use linkedXAxis
in most of these tests
@@ -95,7 +94,7 @@ describe("RunPlot for stochastic", () => { | |||
|
|||
// Generates expected plot data from model | |||
const plotData = wodinPlot.props("plotData"); | |||
const data = plotData(); | |||
const data = plotData(0, 0, 0); |
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.
What's going on with this change?
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.
so WodinPlot.vue
specifies the prop plotData
as type (number, number, number) => WodinPlotData
and it was giving typescript errors because we didnt put 3 args in it even though it doesnt matter but yh technically typescript is correct
i dont think this one has anything super different from the old one, just more of those systematic changes, making sure types and function signatures match!