Closed anku255 closed 5 months ago
It seems like you have done manual testing of this for just a few cases? We need a more robust way of testing and making sure nothing broke. In the MFA branch, we have added story book which helps know about changes in the UI. So make this PR on top of the MFA branch and check the storybook thing to see that nothing broke?
It seems like you have done manual testing of this for just a few cases? We need a more robust way of testing and making sure nothing broke. In the MFA branch, we have added story book which helps know about changes in the UI. So make this PR on top of the MFA branch and check the storybook thing to see that nothing broke?
I have tested it in storybook and in the example app as well. No further changes are required after removing !important
declaration to keep the existing styles.
PS: The styles did break in storybook but I was able to fix that by using similar css loader as we do in our build process.
Summary of change
This PR removes the
!important
declaration from the CSS styles.Test Plan
No further changes were needed after removing the
!important
styles to keep the existing styles. Here is the screenshot after making this change -Documentation changes
(If relevant, please create a PR in our docs repo, or create a checklist here highlighting the necessary changes)
Checklist for important updates
frontendDriverInterfaceSupported.json
file has been updated (if needed)package.json
package-lock.json
lib/ts/version.ts
npm run build-pretty
git tag
) in the formatvX.Y.Z
, and then find the latest branch (git branch --all
) whoseX.Y
is greater than the latest released tag.someFunc: function () {..}
).size-limit
section ofpackage.json
with the size limit set to the current size rounded up.rollup.config.mjs