You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment on the WonderlandContextSelector the profiles are discovered in the create factory method.
This maybe is not so nice since we have the showSelectionIfUnconfigured() fluent closing clause. The user might expect that showSelectionIfUnconfigured() doesn't have the side effect of discovering the profiles in case they are already configured via spring.profiles.active property.
One possible light solution is to have a lazily evaluated discovery, so that only if needed we scan the classpath 🙂
The text was updated successfully, but these errors were encountered:
At the moment on the
WonderlandContextSelector
the profiles are discovered in thecreate
factory method.This maybe is not so nice since we have the
showSelectionIfUnconfigured()
fluent closing clause. The user might expect thatshowSelectionIfUnconfigured()
doesn't have the side effect of discovering the profiles in case they are already configured viaspring.profiles.active
property.One possible light solution is to have a lazily evaluated discovery, so that only if needed we scan the classpath 🙂
The text was updated successfully, but these errors were encountered: