-
-
Couldn't load subscription status.
- Fork 418
Allow multiple dialogs by using the default dialog mechanism in trix #1409
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
base: main
Are you sure you want to change the base?
Conversation
|
Great! I believe the original |
|
It was indeed! It just doesn't fit this purpose, and Trix has its own dialog management, so why tinker :) |
spina.gemspec
Outdated
| gem.add_dependency "jsonapi-serializer" | ||
| gem.add_dependency "browser" | ||
| gem.add_dependency "tailwindcss-ruby" | ||
| gem.add_dependency "tailwindcss-ruby", '< 4.0' |
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.
This makes sense, but it does break projects using Tailwind v4. I should probably upgrade Spina to use Tailwind v4 as well.
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.
It doesn't CI properly unless that's added in at the moment. It does break, and I don't like it being there.
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.
I think the right solution here is to remove this actually, and to upgrade TW in a separate PR, then rebase this and confirm all works and merge.
95a4b9f to
98521be
Compare
Slight design change in the link modal to stop it overlapping other editors.
Primary focus of this PR is to allow multiple buttons to have dialogs by reverting back to the native mechanism in trix.
I've had to add a comment with some tw classes, to force the tailwind builder to see them. Happy to remove, but didn't know a better way to handle that whilst still on older versions of tailwind-ruby/rails and not using the new engine features in importmaps.