-
Notifications
You must be signed in to change notification settings - Fork 19
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
Improving error feedback: reducing the details #25
Comments
Ah, I thought this was a version thing, but it doesn't look like it is - it's when you're passing an object that contains functions (functions passed directly are skipped), when you pass a whole object with functions, that's more difficult to skip over. I'll leave this issue open as there are some improvements in this area coming, but they probably won't be that soon as it's quite involved to work out which bits can be skipped and which not. |
Alright ! Thank you for considering :) I'm not aware of the complexity of the change but wouldn't it be possible to just do the same with the function properties of the "second-level" (since the properties of the "third-level" are replaced by Once again, thanks for the great work ! To reduce the pain: This should help but I foresee some pain when developping components receiving other components as children :P |
Oh, I'm starting to stuggle with the output since I added inline png... It fills my command line with png jibberish :P What would you think of adding a substring to limit the string props output to 20 char or something like that ? I guess I'm not the only one using png. How do other people deal with that ? I'm using this for the test since webpack doesn't pass over the code for tests: require.extensions['.png'] = function () { return null } and I end up with the content in base64 of the png file in the output markup. |
I've run into this issue while integration testing components together with their Redux stores and getting the entire store dumped into my face in case of failure. Makes it very hard to see the actual problem. |
Hi again !
I was wondering if it would be possible to have a flag to reduce the verbosity of the error. Or at least not showing the function definition... Rigth now, because of router stuff, for one test I have this error returned :P
The text was updated successfully, but these errors were encountered: