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

Fix invalid option deprecation checks #956

Conversation

moremada
Copy link
Contributor

The handleOptionDeprecation function is being passed the original props instead of those with the default options merged in. This is causing false positive console.error output to be thrown.

Example:
Any table that doesn't include a responsive props option will see the Invalid option value for responsive. because the check isn't seeing the merged in default option.

The `handleOptionDeprecation` function is being passed the original props instead of those with the default options merged in. This is causing false positive `console.error` output to be thrown.

Example:
Any table that doesn't include a `responsive` props option will see the `Invalid option value for responsive.` because the check isn't seeing the merged in default option.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 76.495% when pulling 9fd450a on moremada:bugfix/invalid-option-deprecation-checks into f0ea9e5 on gregnb:master.

Copy link
Collaborator

@gabrielliwerant gabrielliwerant left a comment

Choose a reason for hiding this comment

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

Nice catch! Thanks for fixing this.

@gabrielliwerant gabrielliwerant merged commit efdab6c into gregnb:master Oct 3, 2019
waqasajaz pushed a commit to waqasajaz/mui-datatables that referenced this pull request Oct 31, 2019
The `handleOptionDeprecation` function is being passed the original props instead of those with the default options merged in. This is causing false positive `console.error` output to be thrown.

Example:
Any table that doesn't include a `responsive` props option will see the `Invalid option value for responsive.` because the check isn't seeing the merged in default option.
lalong13 pushed a commit to lalong13/mui-datatables that referenced this pull request Jan 15, 2020
The `handleOptionDeprecation` function is being passed the original props instead of those with the default options merged in. This is causing false positive `console.error` output to be thrown.

Example:
Any table that doesn't include a `responsive` props option will see the `Invalid option value for responsive.` because the check isn't seeing the merged in default option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants