Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bug: Conditionals are bound via middleware name, not instance #5

Open
HQarroum opened this issue Jan 23, 2024 · 0 comments
Open

Bug: Conditionals are bound via middleware name, not instance #5

HQarroum opened this issue Jan 23, 2024 · 0 comments
Assignees
@HQarroum
Labels
bug Something isn't working framework A label associated with the Lakechain core framework. triage

Comments

@HQarroum
Copy link
Contributor

Expected Behaviour

In the Middleware class, conditionals are associated with middlewares by name, instead of by instance. This could cause confuded conditional retrieval when using multiple instances of the same middleware.

Current Behaviour

Bind conditionals per middleware instance or CDK resource name which are both guaranteed to be unique.

Code snippet

No response

Steps to Reproduce

No response

Possible Solution

No response

Project Lakechain version

latest

Execution logs

No response
@HQarroum HQarroum self-assigned this Jan 23, 2024
@HQarroum HQarroum added bug Something isn't working framework A label associated with the Lakechain core framework. labels Jan 23, 2024
@HQarroum HQarroum moved this to Backlog in Project Lakechain Jan 23, 2024
@HQarroum HQarroum moved this from Backlog to Planned in Project Lakechain Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@HQarroum HQarroum

Labels
bug Something isn't working framework A label associated with the Lakechain core framework. triage
Projects
Project Lakechain
Status: Planned
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HQarroum