-
Notifications
You must be signed in to change notification settings - Fork 6.8k
chore(data-table): hide stability warning in jasmine #4840
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
Conversation
Looping in Jeremy, he requested the data table warning to be a bit more intrusive to make it clear that it's not yet ready |
This isn't part of the sanity checks |
Yeah it isn't really a sanity check but it allows us to disable those warnings in tests. Having the warning super-intrusive just spams the whole tests and doesn't really help at all. I initially only wanted to show the warning in dev-mode only but after chatting with @crisbeto I agreed that it would be nice if developers can disable the warning though |
I'd rather add a check for |
That would work too. But the issue doesn't just appear in Material. Every developer that writes tests using Material will get all of those data-table errors. The sanity checks solution would be kind of temporary until this warning will be removed anyways. But for now it's a super intrusive warning. |
@devversion the warning is in the constructor of the table- they'll only get it if they use the table, which is exactly the point |
@jelbourn Yeah that's clear. But as I mentioned everybody that tests for example a component that contains a |
@jelbourn I'm fine doing the |
0848a5f
to
61031ca
Compare
@andrewseguin @jelbourn Made the requested changes. Please review again. |
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
Can you rebase? |
* No longer shows the data-table stability warning inside of jasmine tests.
61031ca
to
b71b121
Compare
@andrewseguin Done |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Uh oh!
There was an error while loading. Please reload this page.