Skip to content

fix: Datatable onSearch argument use object type #6582

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

Merged

Conversation

hwdsjtu97
Copy link
Contributor

What does this PR do?

update the type of onSearch function in src/js/components/DataTable/index.d.ts

Where should the reviewer start?

What testing has been done on this PR?

yarn test was run

How should this be manually tested?

Do Jest tests follow these best practices?

  • screen is used for querying.
  • The correct query is used. (Refer to this list of queries)
  • userEvent is used in place of fireEvent.
  • asFragment() is used for snapshot testing.

Any background context you want to provide?

What are the relevant issues?

#6555

Screenshots (if appropriate)

Do the grommet docs need to be updated?

No

Should this PR be mentioned in the release notes?

No

Is this change backwards compatible or is it a breaking change?

Breaking change

Copy link
Contributor

@ericsoderberghp ericsoderberghp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this.

Can you also update index.d.ts as well?

@hwdsjtu97
Copy link
Contributor Author

Thanks for working on this.

Can you also update index.d.ts as well?

@ericsoderberghp Hi Eric, which index.d.ts should I update as well?

@ericsoderberghp
Copy link
Contributor

Thanks for working on this.
Can you also update index.d.ts as well?

@ericsoderberghp Hi Eric, which index.d.ts should I update as well?

Oops. My mistake. I confused this with a different review.

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