Closed (fixed)
Project:
Typogrify
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
3 Apr 2020 at 03:25 UTC
Updated:
30 Apr 2020 at 17:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
benjifisherThe current patch on #3124619: Add typogrify.css when the Typogrify filter is used does not touch
typogrify.module, so there is no problem with merge conflicts. I am un-postponing this issue, and I will work on it now.Comment #3
benjifisherThe attached patch implements the Proposed resolution in the issue summary. It completely removes
typogrify.module, so we do not have to worry about coding standards in that file.To test, edit a format (e.g.,
/admin/config/content/formats/manage/basic_html) and enable the Typogrify filter. At the end of the config form, you should see the value of the new constant ('1.0') as in this screenshot:Comment #4
wim leers🥳
An übernit here would be that it should in principle contain
Comment #5
benjifisherThanks for the review. We may as well get it right.
Comment #6
wim leersHehe :)
Comment #7
benjifisher@Wim Leers:
Thanks for reviewing. Sometimes the small changes are dangerous because we get careless.
This patch needs a reroll after #3124616: Fix coding standards in Typogrify. Given the size of the two patches, I am happy to be doing the reroll on this issue. That is, I am glad I decided to fix that issue first.
I am attaching a diff (not an interdiff). The only differences between this patch and the one in #5 is that context lines now use the short array syntax.
I am leaving the status at RTBC. If the testbot does not object, then I will commit this patch.
Comment #9
benjifisher