-
Notifications
You must be signed in to change notification settings - Fork 9
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(magic-block-parser): handle excess table data #78
Conversation
The old magic block syntax allowed shrinking the dimensions of a table, and would leave the data in place. Unknown if that's a bug or a feature. In any event, the new engine should needs to handle that.
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.
These tests are blowing my mind. Made some minor comments/suggestions below. Will re-review after I've checked this out locally!
__tests__/helpers.js
Outdated
}; | ||
|
||
module.exports.silenceConsole = fn => { | ||
const potentialSpies = new Proxy({}, consoleStubHandler); |
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 regret trying to be cute here. I realized you can't use this and not write an expectation, since you have to call the dynamic getter.
const wrap = mount(markdown.react(fx)); | ||
return expect(wrap.html()).toMatchSnapshot(); | ||
|
||
silenceConsole()(error => { |
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.
Is this to quieten the console.logs during testing?
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.
Yes, there's a caught error that prints to error
This PR was released!🚀 Changes included in v6.23.0 |
🧰 Changes
The old magic block syntax allowed shrinking the dimensions of a table,
and would leave the data in place. Unknown if that's a bug or a feature.
In any event, the new engine should needs to handle that.