WRSAT-187 create training program screen #76
Conversation
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
| params = { | ||
| is_in_work_training: "yes", | ||
| work_training_hours: "5", | ||
| work_training_name: "How to do job" |
| expect(page).to have_selector("h1", text: I18n.t("views.work_training.edit.title")) | ||
| choose I18n.t("general.affirmative") | ||
| fill_in I18n.t("views.work_training.edit.work_training_hours_label"), with: "20" | ||
| fill_in I18n.t("views.work_training.edit.work_training_name_label"), with: "The Great British Work Off" |
anisharamnani
approved these changes
Jan 22, 2026
Collaborator
anisharamnani
left a comment
anisharamnani
left a comment
There was a problem hiding this comment.
⭐ creating an additional bug ticket makes sense, thanks jenny for this work!
Collaborator
Author
|
closing to fix heroku app |
Collaborator
Author
|
trying again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is one known issue with this: when you go back to the page (either with "go back" or browser back), the reveal breaks.
^related: the reveals all seem to be broken currently, but i was able to fix that in this PR by calling
revealer.init();on theturbo:loadhook inapplication.js. i don't understand why the reveals were broken in the first place. also, callinghoneycrispInit();in theturbo:loadhook is supposed to fix the js functionality on back AND should includerevealer.init();, but it does not seem to?i'd like to put this in a separate bug ticket because i don't want to get stuck on this one for too long.