Repository navigation
fix(file-size): 🐛 Type FileSize add and subtract as FileSize - #99
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
What
FileSize.addandFileSize.subtractwere typed asNumberValueObject(inherited), although at runtime they return aFileSize. They are now declared asadd(other: FileSize): FileSizeandsubtract(other: FileSize): FileSize.Notes
FileSizeis a closed operation, so the return type is exact.NumberValueObjectis unchanged: its arithmetic can fail on subclass invariants, sothiswould be a wrong promise there.clone(), so subclasses ofFileSizekeep their own type at runtime.size.add(100)with a plain number no longer compiles. Passnew FileSize(100).FileSizeupdated with the new signatures and the negative-result error.Verification
yarn test,yarn buildpass. Coverage stays at 100%. The arithmetic test callsFileSize.to()on the results, so it only compiles if both returnFileSize.