Skip to content

[ISSUE] Inject Meta Data into use case calls #9

@envimate-opensource

Description

@envimate-opensource

There are use cases that require data from the request's meta data map. One example would be giving the UserId from the JwsToken inside the authorization header as parameter to use cases, which adapt their logic based on the requesting user.

I would like to define for each use case (or a general mapping if applicable), which additional parameter are given and how they are obtained.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions