.NET standard interfaces#41
Merged
Seramis merged 1 commit intoByteAether:mainfrom Apr 27, 2026
Merged
Conversation
…xValue` and introduced `MinValue` for as required by standard `IMinMaxValue<T>` interface. Marked `Max` as obsolete. Synced README and PACKAGE files with updates. Added and adjusted unit tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Introduced relevant .NET standard interfaces. Replaced
MaxwithMaxValueand introducedMinValuefor as required by standardIMinMaxValue<T>interface. MarkedMaxas obsolete. Synced README and PACKAGE files with updates. Added and adjusted unit tests.Type of Change
Checklist
main)..editorconfig)Additional Notes
ulid.Maxhas been marked as obsolete -ulid.MaxValueis the property that should be used based on .NET'sIMinMaxValue<>interface.ulid.Emptyis kept for semantic clarity.