Skip to content

Conversation

@MrAgeo
Copy link
Contributor

@MrAgeo MrAgeo commented Apr 5, 2024

This PR removes the ArgumenNullException present in ConfigSettingEntry.GetAcceptedValues(AcceptableValueBase values), enforcing the use of both MinValue and MaxValue for custom range classes (see issue's comments for a in-depth explanation)

MrAgeo added 3 commits April 5, 2024 01:25
- Added `supportedTypes` Type array (containing the types of `AcceptableValueList` & `AcceptableValueRange`).

- Added method `isTypeSupported` to check if a type is a subclass or an instance of a type in `supportedTypes` via `IsSubclassOfRawGeneric`.

- Added `IsSubclassOfRawGeneric(Type generic, Type toCheck)` method which checks if `toCheck` is a subclass or an instance of `generic`.
…ue` fields for a custom range class

See issue's comments for a in-depth explanation
@ManlyMarco ManlyMarco changed the title Fix for issue #88 Do not throw ArgumenNullException in ConfigSettingEntry.GetAcceptedValues Apr 5, 2024
@ManlyMarco ManlyMarco merged commit 19cff15 into BepInEx:master Apr 5, 2024
@MrAgeo MrAgeo deleted the fix-for-issue88 branch April 5, 2024 23:44
starfi5h pushed a commit to starfi5h/BepInEx.ConfigurationManager that referenced this pull request Oct 31, 2025
…lues (BepInEx#89)

This PR removes the ArgumenNullException present in ConfigSettingEntry.GetAcceptedValues(AcceptableValueBase values), enforcing the use of both MinValue and MaxValue for custom range classes (see issue's comments for a in-depth explanation)

Fixes BepInEx#88

(cherry picked from commit 19cff15)
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.

2 participants