Allow registering only specific action groups#1
Open
klaustopher wants to merge 1 commit into
Open
Conversation
Adds an optional second argument to TurboPower.initialize() so consumers
can enable a subset of actions instead of all or nothing:
TurboPower.initialize(Turbo.StreamActions, [AttributeActions, BrowserActions])
Each module now exposes a named ActionGroup constant (AttributeActions,
BrowserActions, etc.) wrapping its existing register function. When no
groups are passed, all groups are registered as before. The morph action
from turbo-morph is always registered.
Closes marcoroth#20
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@klaustopher made an upstream PR based on this work: marcoroth#333 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds an optional second argument to TurboPower.initialize() so consumers can enable a subset of actions instead of all or nothing:
Each module now exposes a named ActionGroup constant (AttributeActions, BrowserActions, etc.) wrapping its existing register function. When no groups are passed, all groups are registered as before. The morph action from turbo-morph is always registered.
Ticket
What are you trying to accomplish?
Screenshots
What approach did you choose and why?
Merge checklist