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

DTSPB-4411: Back button spike #2280

Draft
wants to merge 21 commits into
base: master
Choose a base branch
from

Conversation

jamiealbertelli
Copy link
Contributor

Before creating a pull request make sure that:

  • commit messages are meaningful and follow good commit message guidelines
  • README and other documentation has been updated / added (if needed)
  • tests have been updated / new tests has been added (if needed)
  • update CSS version to force refresh if any changes are introduced

Please remove this line and everything above and fill the following sections:

JIRA link (if applicable)

Change description

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[ ] No

@jamiealbertelli jamiealbertelli marked this pull request as draft November 15, 2024 16:04
@@ -4,13 +4,21 @@
{% from "govuk/components/button/macro.njk" import govukButton %}

{% block form_content %}
<h1 class="govuk-fieldset__legend--l">
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is temporary code to conditionally display the content.question depending on whether the journey is oneOtherExec or MultipleExec. I couldn't get any expression to work in the fieldset text object, nor would a neat one-liner ternary expression work here. This is something for the full mutli-exec work assignee to think about.



<pre>{{ fields | dump | safe }}</pre>

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The for loop below is existing behaviour for displaying all the executors but since the logic for entering the exec name now takes place in /executor-names this needs the be worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant