Skip to content

fix: check API settings values before storing them in the SettingsProvider #48

Open
@andreaforni

Description

@andreaforni

The SettingsProvider loads the backend's setting configuration (apiSettings) into its state.
Many of those fields are parsed into numbers using Number function (here and there). There is no check to see if the field is undefined before converting it, this may result in NaN values stored inside the provider.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions