Make hub resolving is lazy#117
Open
7-zete-7 wants to merge 1 commit into
Open
Conversation
7-zete-7
force-pushed
the
lazy-hub-resolving
branch
4 times, most recently
from
March 25, 2026 11:38
6c6d921 to
bce6303
Compare
7-zete-7
force-pushed
the
lazy-hub-resolving
branch
from
March 25, 2026 11:40
bce6303 to
913fcfb
Compare
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
1 participant
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.
The current implementation of builtin Hub detection doesn't support the use of
env(...)(see dunglas/symfony-docker#869 (comment)). With this PR, I propose adding lazy detection of the appropriate implementation based on the values of envs at runtime ifenv(...)is used.