-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend rename transform to skip primitives #4684
Comments
@ardatan, @gilgardosh, this sounds like a good enhancement to me. Let us know your thoughts, I'd be happy to raise a PR if you are like this functionality. |
Turned out the issue here was that The PR below fixes these issues, hence this ticket can be closed: |
Available in the latest release! |
Is your feature request related to a problem? Please describe.
When using a number of different data sources, its nice to have a consistent name pattern between types under 1 source. Sometimes this can be handled by the prefix transform, but often you may want slightly more specific control
Describe the solution you'd like
Along side config value
useRegExpForTypes
, have askipPrimitives
key.This can either be
true
, to skip all or an array to define the exact primitives to skip when renaming.Example
Which would result in
In this above case, using the prefix plugin alone with
value: v1_Banana
would result in queryv1_Bananauser
which we dont wantDescribe alternatives you've considered
Adding more configurability to prefix transform, or a stand alone plugin. Both I think arnt as nice as this option in the rename plugin.
Additional context
The text was updated successfully, but these errors were encountered: