-
Notifications
You must be signed in to change notification settings - Fork 1
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
[#60359] Harmonise FeedbackDialog slot naming #219
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: dae6eae The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Renames the `additional_content` slot to `additional_details` to make Feedback Dialog consistent with the newly introduced Danger Confirmation Dialog. ViewComponent defines a `with_SLOT_NAME_content` method for given slots. Using `additional_content` as a slot name results in a `with_additonal_content_content` method being generated - this makes for a poor API for component users.
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.
Please add a changeset and fix the CI. Otherwise good 👍
previews/primer/open_project/feedback_dialog_preview/additional_content.html.erb
Show resolved
Hide resolved
3e38519
to
a1b641c
Compare
ef42f27
to
d11d468
Compare
Makes naming of Feedback Dialog preview templates consistent with those used by newly introduced Danger Confirmation Dialog.
d11d468
to
dae6eae
Compare
What are you trying to accomplish?
Renames the
additional_content
slot toadditional_details
to make Feedback Dialog consistent with the newly introduced Danger Confirmation Dialog.ViewComponent defines a
with_SLOT_NAME_content
method for given slots. Usingadditional_content
as a slot name results in awith_additonal_content_content
method being generated - this makes for a poor API for component users.Screenshots
End users should not see any visual changes.
Integration
This will require update of opf/openproject See PR: opf/openproject#17568
List the issues that this change affects.
Closes https://community.openproject.org/work_packages/60359
Risk Assessment
What approach did you choose and why?
Anything you want to highlight for special attention from reviewers?
Accessibility
Merge checklist