This repository was archived by the owner on Oct 13, 2024. It is now read-only.
Added Strict Equality (===) & Inequality (!==) Checks#17
Merged
Conversation
shashankbhosagi
approved these changes
Jul 11, 2023
Member
shashankbhosagi
left a comment
There was a problem hiding this comment.
That's great, Good Work✨
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PR Summary
This commit adds strict equality and inequality checks to the codebase. These checks are more accurate than the loose equality (==) and inequality (!=) checks that were previously used. This will help to prevent errors in the code and make it more robust.
Benefits: The benefits of using strict equality and inequality checks include:
Increased accuracy: The strict checks are more accurate than the loose checks, and will help to prevent errors in the code.
Increased robustness: The strict checks will make the code more robust, and less likely to be affected by unexpected changes.
Types of Changes
What types of changes does your code introduce to this project? Please mark with
an
xthe applicable boxes.Bugfix (non-breaking change that addresses an issue)
New feature (non-breaking change that adds functionality)
Breaking change (fix or feature that may cause existing functionality to
break)
Documentation update
Refactoring (code optimization or restructuring)
Other (please specify): __________
Testing and Publishing
Please indicate the status of the following:
These changes have been thoroughly tested.
Code is properly formatted using command
deno fmt