-
Notifications
You must be signed in to change notification settings - Fork 9
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
Admin: Enrollment View #2327
Closed
Closed
Admin: Enrollment View #2327
Conversation
This file contains 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
github-actions
bot
added
back-end
Django views, sessions, middleware, models, migrations etc.
deployment-dev
[auto] Changes that will trigger a deploy if merged to dev
labels
Aug 28, 2024
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
angela-tran
force-pushed
the
feat/in-person-enrollment-view
branch
9 times, most recently
from
September 3, 2024 22:35
9e4a27b
to
8a37a63
Compare
angela-tran
force-pushed
the
feat/in-person-enrollment-view
branch
3 times, most recently
from
September 4, 2024 18:35
1d62d10
to
66c859f
Compare
this is so it can be reused in `enrollment.index` and `in_person.enrollment` when they receive a GET request.
this is needed temporarily while the eligibility view is still being worked on.
the card tokenization flow listens for the `element`'s click event before it will set the iframe `src`. use a Promise to wait for the card tokenization function to finish and then programmatically click the button which is not displayed to the user.
this allows form submission to go through, but it is currently POST-ing to the Benefits view functions; further refactoring will be done to change that.
for CardTokenizeSuccessForm
form submission now POSTs to the in_person `enrollment` view function, which does not handle POSTs just yet.
reuse it in the `in_person.enrollment` view. this gets us back to having a working form submission in the in-person enrollment view, but we need to be able to configure which templates to return for the various success / error scenarios.
angela-tran
force-pushed
the
feat/in-person-enrollment-view
branch
from
September 4, 2024 19:28
e827645
to
80369e6
Compare
This was referenced Sep 5, 2024
thekaveman
removed this from the Admin tool: in-person eligibility verification milestone
Sep 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
back-end
Django views, sessions, middleware, models, migrations etc.
deployment-dev
[auto] Changes that will trigger a deploy if merged to dev
front-end
HTML/CSS/JavaScript and Django templates
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.
Closes #2244
WIP