feat(rails): load enabled rail plugins end to end#2187
Draft
Pouyanpi wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Pouyanpi <13303554+Pouyanpi@users.noreply.github.com>
This was referenced Jul 17, 2026
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
11 tasks
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
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.
Description
Load enabled rail plugins through the complete configuration and runtime path.
Index packaged plugin flow sources by Colang version, include plugin-declared
configuration fields when constructing
RailsConfig, and load only flows fromplugins explicitly enabled by configuration.
Stack 3 defines how a catalog can be extended with named plugin entry points;
this PR carries that explicit enablement through configuration construction and
runtime flow loading. Discovery and activation stay separate: installing a
plugin does not make its config fields or flows active by default.
Add an end-to-end example plugin suite covering disabled plugins, enabled
configuration projection, flow loading, configured-surface parameters,
collisions, unknown plugins, cache resets, and both Colang dialects. Static
catalog discovery remains cheap and does not import action modules.
Impact
in the application configuration.
flow source to the same paths used by built-in rails.
RailsConfig, load flow files, or import actionmodules.
have deterministic, tested behavior.
and runtime behavior.
Stack
pouyanpi/rail-library-stack-3-manifest-contractdeveloppouyanpi/rail-library-stack-4-builtinspouyanpi/rail-library-stack-4b-flow-gatepouyanpi/rail-library-stack-5-lazy-actionspouyanpi/rail-library-stack-6-hardeningRelated Issue(s)
Verification
AI Assistance
Checklist