Repository navigation
feat: Ensure Nextcloud code use strict comparaison - #105
Merged
Merged
Conversation
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
nickvergessen
approved these changes
Sep 3, 2026
CarlSchwan
force-pushed
the
carl/strict-comparaison
branch
from
September 24, 2026 12:26
da15883 to
63c145d
Compare
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
CarlSchwan
force-pushed
the
carl/strict-comparaison
branch
from
September 24, 2026 13:34
63c145d to
fe01cc6
Compare
come-nc
reviewed
Sep 24, 2026
come-nc
approved these changes
Oct 1, 2026
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
come-nc
force-pushed
the
carl/strict-comparaison
branch
from
October 14, 2026 14:37
d3ae134 to
fcdc994
Compare
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
3 participants
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
Add
strict: truetoin_arraywhen possibleUse
===and!==instead of==and!=Motivation and context
Security and correctness
How has this been tested?
Types of changes
PR checklist