-
Notifications
You must be signed in to change notification settings - Fork 60
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
coral: implement form component [#141] #159
Conversation
b08ea2a
to
10b4736
Compare
10b4736
to
deceda4
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.
LGTM, but would be great if we would render the component in this PR or then we could frop the login components from this PR to the followup.
Also, a rebase it needed.
@testing-library/user-event has a peerDep for @testing-library/dom but it's a different version than the one that @testing-library/react uses and brings in as a devDep. Solution based on research on GitHub shows we can either ignore the warning in pnpm or install the @testing-library/dom as devDep in the version that @testing-library/react uses it. I did the latter hoping that in one of the next versions of @testing-library/user-event this will be resolved. see testing-library/user-event#438 (comment) testing-library/user-event#551 (comment)
- remove use of 'any' type - add stricter rule for use of any for linting
- `index.tsx` should be reserved for resource root - files for pages can live on first level in `pages` - rename files to match naming conventions for react - update documentation to be more explicit and correct
b3f54d6
to
2d27275
Compare
│ │ ├── page-one | ||
│ │ ├── ... | ||
│ │ └── index.ts | ||
│ │ ├── index.tsx |
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 don't think want to even try to keep this up to date with current implementation so lets keep the examples abstract.
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.
But we can do this later 👍
Resolves: #141
About this change - What it does
Adds a
Form.tsx
component based on a solution created for aiven-core.Why this way
Form.tsx
only implements the functionality we need for Klaw.esModuleInterop
to true. Otherwise jest won't be able to handle it.allowSyntheticDefaultImports: true
because that's set to true when usingesModuleInterop
ℹ️ for review
any
any
is now an error