Visitar URL original
Intercept Reflection exceptions from `AppSettingsConfigurationStore` by jnyrup · Pull Request #1210 · fluentassertions/fluentassertions · GitHub
Skip to content

Intercept Reflection exceptions from AppSettingsConfigurationStore - #1210

Merged
jnyrup merged 1 commit into
fluentassertions:masterfrom
jnyrup:configurationStoreInterceptor
Dec 29, 2019
Merged

jnyrup merged 1 commit into
fluentassertions:masterfrom
jnyrup:configurationStoreInterceptor

Conversation

@jnyrup

@jnyrup jnyrup commented Dec 29, 2019

Copy link
Copy Markdown
Member

Some platforms throw reflection exceptions when trying to use ConfigurationManager.
This does not fix the underlying problem of not being unable to use ConfigurationManager, but returns null instead of an exception.

Relates to #1207 and #1151

Some platforms throws reflection exceptions when trying to use `ConfigurationManager`.
This does not fix the underlying problem of not being unable to use `ConfigurationManager`, but returns `null` instead of an exception.

Relates to fluentassertions#1207 and fluentassertions#1151
@jnyrup
jnyrup force-pushed the configurationStoreInterceptor branch from 8c97ed4 to eaa952f Compare December 29, 2019 16:03
@jnyrup
jnyrup merged commit 4607f79 into fluentassertions:master Dec 29, 2019
@jnyrup
jnyrup deleted the configurationStoreInterceptor branch December 29, 2019 16:15
@SteveBush

Copy link
Copy Markdown

Current fix returns null for GetSettings but NullConfigurationStore returns an empty string. Seems like a more consistent fix would be to emulate NullConfigurarion store behavior.

@jnyrup

jnyrup commented Jan 2, 2020

Copy link
Copy Markdown
Member Author

@SteveBush I see the inconsistency.
The code here was intentional, as AppSettingsConfigurationStore can return null.
Are having problems with the merged fix?

@SteveBush

SteveBush commented Jan 4, 2020 via email

Copy link
Copy Markdown

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.

3 participants