EverestAPI / EverestAPI/Everest
Reading or setting a null flag should be considered invalid
Open
enhancement
- Dominant language
- C#
- Stars
- 516
- Forks
- 106
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 5
Description
### I am planning on implementing this myself
Yes
### Describe your request
Flags are always assumed to be non-`null` strings, even though `null` flags are technically valid. As such, reading or setting a `null` flag should in my opinion be considered a bug in the caller.
Everest should no longer support reading or setting a `null` flag and instead throw an `ArgumentNullException` in this situation.
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.