-
Notifications
You must be signed in to change notification settings - Fork 8
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
Feature/shadcn skeleton #732
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
<button id="setFindById1" onClick={() => setFindBy("1")} /> | ||
<button id="setFindById2" onClick={() => setFindBy("2")} /> | ||
<button style={{ width: 1, height: 1 }} id="setFindById1" onClick={() => setFindBy("1")} /> | ||
<button style={{ width: 1, height: 1 }} id="setFindById2" onClick={() => setFindBy("2")} /> |
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.
Shouldn't buttons have a default style that makes them have dimensions and be findable? this works but i wouldn't have thought it was necessary. Could the issue be that something is on top of the buttons?
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.
Because there is no label or text inbetween the button, it won't have anything.
If we did hello then the button will take up the space of the hello
|
||
interface AutoSuiteConfig { | ||
name: string; | ||
adapter: AutoAdapter; | ||
wrapper: ComponentType<{ children: ReactNode }>; | ||
} | ||
|
||
const ONLY_RUN_SUITES = { | ||
[SUITE_NAMES.SHADCN]: ["AutoButton"], |
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 am down for this, but it does mean all the autoinputs stuff that is landing in this PR is untested for 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.
Yes it is untested for now. I am bringing <autoform />
in soon, which will include some cypress tests for the autoInput and will take a look at what we have for jests if we do and convert it. Just trying to get some stability
The Shadcn Skeleton which gives us the ability to integrate Shadcn and Gagdet
PR Checklist
Occasionally that error was coming up so added
width
&height
Also added a click & Type command as was experiencing issues with Shadcn input components in cypress
cypress-io/cypress#5830
cypress-io/cypress#5827