Skip to content
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

Merged
merged 4 commits into from
Jan 22, 2025
Merged

Feature/shadcn skeleton #732

merged 4 commits into from
Jan 22, 2025

Conversation

jadewale
Copy link
Collaborator

@jadewale jadewale commented Jan 22, 2025

The Shadcn Skeleton which gives us the ability to integrate Shadcn and Gagdet

PR Checklist

  • Important or complicated code is tested
  • Any user facing changes are documented in the Gadget-side changelog
  • Any immediate changes are slated for release in Gadget via a generated package dependency bump
  • Versions within this monorepo are matching and there's a valid upgrade path

Occasionally that error was coming up so added width & height
Screenshot 2025-01-22 at 08 22 46

Also added a click & Type command as was experiencing issues with Shadcn input components in cypress
cypress-io/cypress#5830
cypress-io/cypress#5827

@jadewale jadewale requested a review from airhorns January 22, 2025 13:18
Copy link
Contributor

@airhorns airhorns left a 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")} />
Copy link
Contributor

@airhorns airhorns Jan 22, 2025

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?

Copy link
Collaborator Author

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"],
Copy link
Contributor

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?

Copy link
Collaborator Author

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

@jadewale jadewale merged commit 506d80b into main Jan 22, 2025
9 checks passed
@jadewale jadewale deleted the feature/shadcn-skeleton branch January 22, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants