Skip to content
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

Release 8.3.0 #292

Merged
merged 1 commit into from
Oct 12, 2023
Merged

Release 8.3.0 #292

merged 1 commit into from
Oct 12, 2023

Conversation

jkempster34
Copy link
Contributor

@jkempster34 jkempster34 commented Oct 12, 2023

Release version 8.3.0 which includes the fixes to abbreviations inside call to action and legislative list components.


This repo is owned by the publishing platform team. Please let us know in #govuk-publishing-platform when you raise any PRs.

@jkempster34 jkempster34 merged commit 58b4417 into main Oct 12, 2023
6 checks passed
@jkempster34 jkempster34 deleted the release-8.3.0 branch October 12, 2023 09:26
jkempster34 added a commit that referenced this pull request Jan 24, 2024
We use the default mechanism for parsing so that the parser can handle
abbreviations and footnotes inside call to action component.

Since this change (#292)  we have had a regression where defining a call to
action on a single line does not work as expected (e.g., `$CTA Click here to
start the program $CTA`). The closing `div` is evaluated as markdown and the
call to action component therefore runs on until the next closing `div`.

This can be fixed by adding in some new lines between the div tags.
jkempster34 added a commit that referenced this pull request Jan 24, 2024
We use the default mechanism for parsing so that the parser can handle
abbreviations and footnotes inside call to action component.

Since this change (#292) we have seen a regression where defining a call to
action on a single line does not work as expected (e.g., `$CTA Click here to
start the program $CTA`). The closing `div` is evaluated as markdown and the
call to action component therefore runs on until the next closing `div`.

This can be fixed by adding in some new lines between the div tags.
jkempster34 added a commit that referenced this pull request Jan 24, 2024
We use the default mechanism for parsing so that the parser can handle
abbreviations and footnotes inside call to action component.

Since this change (#292) we have seen a regression where defining a call to
action on a single line does not work as expected (e.g., `$CTA Click here to
start the program $CTA`). The closing `div` is evaluated as markdown and the
call to action component therefore runs on until the next closing `div`.

This can be fixed by adding in some new lines between the div tags.
jkempster34 added a commit that referenced this pull request Jan 24, 2024
We use the default mechanism for parsing so that the parser can handle
abbreviations and footnotes inside call to action component.

Since this change (#292) we have seen a regression where defining a call to
action on a single line does not work as expected (e.g., `$CTA Click here to
start the program $CTA`). The closing `div` is evaluated as markdown and the
call to action component therefore runs on until the next closing `div`.

This can be fixed by adding in some new lines between the div tags.
jkempster34 added a commit that referenced this pull request Jan 24, 2024
We use the default mechanism for parsing the call to action component so that
the parser handles abbreviations and footnotes within.

Since this change (#292) we have seen a regression where defining a call to
action on a single line does not work as expected (e.g., `$CTA Click here to
start the program $CTA`). The closing `div` is evaluated as markdown and the
call to action component therefore runs on until the next closing `div`.

This can be fixed by adding in some new lines between the div tags.
jkempster34 added a commit that referenced this pull request Jan 24, 2024
We use the default mechanism for parsing the call to action component so that
the parser handles abbreviations and footnotes within.

Since this change (#292) we have seen a regression where defining a call to
action on a single line does not work as expected (e.g., `$CTA Click here to
start the program $CTA`). The closing `div` is evaluated as markdown and the
call to action component therefore runs on until the next closing `div`.

This can be fixed by adding in some new lines between the div tags.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants