-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add expect enum usage #2370
Add expect enum usage #2370
Conversation
9b85560
to
dee4256
Compare
export const EXPECT_SAME = 'expect_same'; | ||
|
||
const hostExepectations = [EXPECT, EXPECT_ENUM]; |
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 quick question here, we have multiple files in model directory.
Like cluster.js, sapSystem.js and index.js
What kind of data should we always put in index.js?
For now, it is mostly cluster details view related.
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.
well, that's subjective, as long as it doesn't go out of control having one file is convenient
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.
Nice jooob!
LGTM
Description
Add
expect_enum
results usage. This means that the host expectations are now ofexpect
andexpect_enum
, and the results in the result detail view could be of warning type.Example in storybook:
How was this tested?
Tested with UT