Skip to content

fix: bind UserContextServiceInterface instead of UserContextInterface in Objects.yaml - #53

Draft
gradinarufelix wants to merge 1 commit into
flownative:mainfrom
gradinarufelix:feature-objects-yaml-fix
Draft

fix: bind UserContextServiceInterface instead of UserContextInterface in Objects.yaml#53
gradinarufelix wants to merge 1 commit into
flownative:mainfrom
gradinarufelix:feature-objects-yaml-fix

Conversation

@gradinarufelix

Copy link
Copy Markdown
Contributor

DefaultUserContextService implements UserContextServiceInterface, which is also the interface SentryClient injects. The previous Objects.yaml binding targeted the UserContext value-object interface — which DefaultUserContextService does not implement — and only worked because Flow's implicit single-implementation resolution happened to pick the right class for the injected interface.

One-line fix, no behavior change; it just makes the intended binding explicit.

… in Objects.yaml

DefaultUserContextService implements UserContextServiceInterface, which is
also the interface SentryClient injects. The previous binding targeted the
UserContext value-object interface and only worked through Flow's implicit
single-implementation resolution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant