This repository was archived by the owner on Jul 28, 2023. It is now read-only.
Add server side negation operator#214
Merged
luisherranz merged 3 commits intomain-wp-directives-pluginfrom Apr 18, 2023
Merged
Conversation
23 tasks
SantosGuillamot
approved these changes
Apr 18, 2023
Contributor
SantosGuillamot
left a comment
There was a problem hiding this comment.
I've tested it an it works as expected. Looks good to me 🙂
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.
2 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.
What
The server-side part of the
!operator introduced in #213.Why
Because the server also needs to understand it.
How
Just replicate the JavaScript logic, check for the presence of
!at the start of the $path and return the opposite if it's found.