-
Notifications
You must be signed in to change notification settings - Fork 4
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
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator #1037
Draft
MichaelKetting
wants to merge
11
commits into
develop
Choose a base branch
from
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator #1037
MichaelKetting
wants to merge
11
commits into
develop
from
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator
Conversation
This file contains 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
MichaelKetting
force-pushed
the
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator
branch
4 times, most recently
from
February 26, 2024 09:40
eadcd51
to
fc4bad7
Compare
MichaelKetting
force-pushed
the
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator
branch
from
March 6, 2024 14:41
2c93ad1
to
89329d7
Compare
TypePipe uses an older implementation of PEVerify lookup. In order to reduce development dependencies, removing this dependency from the unit tests unlinks this dependency chain.
… to break dependency on ITypeResolutionService. Note that since there is a dependency between type discovery configuration and type resolution, the relevant customizations must be dropped here. The configuration of the feature will be restored once ITypeDiscoveryService can be resolved via IoC container.
…sts and then the removal of ContextAwareTypeUtility
MichaelKetting
force-pushed
the
feature/RM-5931-Support-for-Bootstrapping-in-ServiceLocator
branch
from
April 18, 2024 07:22
89329d7
to
0d8cb2e
Compare
MichaelKetting
force-pushed
the
develop
branch
from
August 14, 2024 08:28
d221533
to
147fb1d
Compare
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.
https://re-motion.atlassian.net/browse/RM-5931
DefaultServiceLocator.CreateWithBootstrappedServices()
should be moved to development helpers. Production code should register defaults withBootstrapServiceConfiguration
.RegisterAssemblyFilter
-API toIBootstrapServiceConfiguration
forIAssemblyLoaderFilter
, that allows settingAddIgnoredAssembly
,ShouldConsiderAssembly
,ShouldIncludeAssembly
via fluent API.RegisterSpecificRootAssemblies
-API toIBootstrapServiceConfiguration
forIRootAssemblyFinder
that sets upSpecificRootAssemblies
. Creates fixedTypeDiscoveryServiceConfiguration.SpecificRootAssemblies.CreateRootAssemblyFinder(new FilteringAssemblyLoader(new LoadAllAssemblyLoaderFilter()))
. Remove the related Config-parts fromTypeDiscoveryServiceConfiguration
(Mode
andCreateTypeDiscoveryService
).TypeDiscoveryServiceConfiguration.SpecificRootAssemblies
with fluent API by extendingRegisterSpecificRootAssemblies
with a fluent return type.RegisterLogging
-API toIBootstrapServiceConfiguration
forILogManager
, accepting theILogManager
as a parameter.ILogManager
fromIBootsrapSerivceConfiguration
viaGetLogManager()
extension method