-
Notifications
You must be signed in to change notification settings - Fork 648
Allow rowspan and colspan in markdown table rendering #1870
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
Allow rowspan and colspan in markdown table rendering #1870
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jtgeibel (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
@jtescher Thanks for your contribution! This change looks good to me, but I don't have access to merge and deploy it – some other member of the team will do so soon. The only thing I'm wondering about is why we don't use ammonia's defaults – they look reasonable to me, and would avoid a bunch of other rendering issues. This is of course unrelated to this PR, and in my opinion we can merge this as it is. CC @jtgeibel |
I'm actually a bit confused about why percy is failing this, this PR definitely shouldn't have affected download count graphs |
I restarted the Frontend job and Percy is happy now, so I'm guessing this was a transient issue on their end. @smarnach Looking just at the I agree these changes are good to merge. |
📌 Commit ecb2877 has been approved by |
…tgeibel Allow rowspan and colspan in markdown table rendering Allow `rowspan` and `colspan` attributes of forms in READMEs. Fixes #1863
☀️ Test successful - checks-travis |
I was assuming that the differences in the chart were caused by changes to Google Charts. We use the deprecated @jtgeibel Yes, we currently do allow a few additional things, e.g. the I will open an issue for this for further discussion. |
Allow
rowspan
andcolspan
attributes of forms in READMEs.Fixes #1863