-
Notifications
You must be signed in to change notification settings - Fork 1
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.
I believe this item includes creating a Storybook Site that will be kept up-to-date with main branch. Can you add the necessary github actions for that as well?
@yen-tt I added the workflow to this. I'll add the ci config in that branch directly in a separate pr |
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.
As part of SLAP-2442, we'll want to add Yext-specific styling to the Storybook Site. This requires adding some things to the .storybook directory. You can see what we did to add the Yext branding/styling to the Search UI React Site here: yext/search-ui-react@e3d1259.
I think we should keep this PR as is. It's goal is to add Storybook to the repo. Then, you'll have a second PR (once the Address is merged in), creating Address Stories and the Yext branding.
J=SLAP-2442 TEST=manual checked-out address and ran without errors
7c5a07e
to
a0414fb
Compare
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.
looks like several tests are failing. I thought they should all (or almost all) be passing now?
ba8f06e
to
62069c0
Compare
@nmanu1 jest tests will also fail because there are currently no tests |
I thought a test was added for the Address component, which is now in main? Shouldn't at least the |
The checks say no tests were found. Percy fails because there are no stories yet, I will add address stories in a separate PR after Storybook is merged |
package.json
Outdated
], | ||
"moduleDirectories": [ | ||
"node_modules", | ||
"<rootDir>" | ||
], | ||
"testEnvironment": "jsdom", |
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 is this no longer needed?
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.
it was specified on the other branch
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.
not sure I follow. it looks like all other branches/changes have been merged into main. so, won't this delete the line from main?
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.
this is the same concern I had for the test file that's being deleted too
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.
@nmanu1 I added it back
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.
ok! so the tests
checks should pass now, right?
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.
actually it looks like there's an error because of the file extensions in the Jest config
package.json
Outdated
@@ -56,10 +83,11 @@ | |||
], | |||
"transform": { | |||
"\\.[jt]sx?$": "ts-jest" | |||
}, | |||
"globals": { | |||
"ts-jest": { |
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.
looks like specifying the ts-jest
config under globals
is deprecated and should be moved according to 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.
yes just fixed that. ready now
Setting up storybook with the vite-builder plugin
J=SLAP-2442
TEST=manual
checked-out address and ran without errors