Skip to content
This repository was archived by the owner on Apr 2, 2024. It is now read-only.

Conversation

@niksajakovljevic
Copy link
Contributor

There were two problems with async flag. First it was present
in two Config structs and parsed in the struct that is not being
used. Second was that async flag was not passed when creating
sub-config structure. This resulted in async flag not being
applied.

Also removing some unused config.

Hopefully in future we will increase test coverage for flags and configs so we catch this easily.
It seems we would need a decent amount of refactoring to support these tests so I'll leave it for another PR.

There were two problems with async flag. First it was present
in two Config structs and parsed in the struct that is not being
used. Second was that async flag was not passed when creating
sub-config structure. Effectively result in async flag not being
applied. This should fix that.
@niksajakovljevic niksajakovljevic added the Bug Something isn't working label Jan 3, 2022
Copy link
Contributor

@VineethReddy02 VineethReddy02 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@niksajakovljevic niksajakovljevic merged commit 12ec0c9 into master Jan 3, 2022
@niksajakovljevic niksajakovljevic deleted the niksa/pass-async-flag branch January 3, 2022 13:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants