Export Custom Operators #656
Merged
Conversation
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
1 participant
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.
Provides a workaround for SR-12132 which causes custom operators defined in
FluentKitto not be exported correctly (fixes vapor/fluent-kit#144, #656)Custom operators for String filtering will now be available by importing just
Fluent:~~: Value contains string=~: Value has string prefix~=: Value has string suffix!~: Value doesn't contain string!=~: Value doesn't have string prefix!~=: Value doesn't have string suffixAs well as operators for Array filtering:
~~: Value in array!~: Value not in array