-
Notifications
You must be signed in to change notification settings - Fork 6
Taxonomy email alert signup pages #33
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
Merged
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
1f7225e
Upgrade RSpec from 3.2 to 3.5
1c7c665
Clean up cucumber test setup
674af22
Mock out email-alert-api in features with a verifying double
37ecea4
Use mock email-alert-api in email alert feature, also test redirects
7e9934e
Upgrade ruby version from 2.3.0 to 2.3.1
ddd8af9
Add email signup flow and associated cucumber feature
0a13d1f
Update frontend toolkit and add elements
c4eef7d
Add markup, copy tweaks and styling
e678a52
Add show/hide content
e5d9bad
Remaining frontend work to implement design from prototype
5a36406
Amend taxon key used when creating subscription
ce64de0
Add slimmer to rspec setup
1db8521
Make naming of signup query param more consistent
a9b2a45
Add some additional testing of TaxonomySignupsController
9d04d85
Frontend tweaks to taxonomy email signup pages
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 2.3.0 | ||
| 2.3.1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| //= require show-hide-content.js | ||
| ;(function () { | ||
| $('.js-hidden-submit').removeClass('js-hidden-submit') | ||
| $('.no-js-panel').removeClass('no-js-panel') | ||
| $('.no-js-hidden-submit').addClass('js-hidden-submit') | ||
| $('.js-hidden-submit').attr('aria-hidden', 'false') | ||
| var showHideContent = new GOVUK.ShowHideContent() | ||
| showHideContent.init() | ||
| })() |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
We're currently not using GOV.UK Elements on any GOV.UK Publishing frontend applications.
Seems as though the kind of UI you're implementing it makes sense to make use of Elements, just Elements is technically built in a different way to the rest of GOV.UK Publishing frontend.
Maybe let's have a chat through it offline
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.
As far as I know you don't have or hardly have anything like this on GOV.UK. Looks like you had a chat about it though, so that's good.