Skip to content
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.

Sign up for GitHub

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

Jump to bottom

We shouldn't keep track of the current JsonPath if there is no need for it #81

Closed
Breus opened this issue Mar 4, 2024 · 0 comments · Fixed by #82
Closed

We shouldn't keep track of the current JsonPath if there is no need for it #81

Breus opened this issue Mar 4, 2024 · 0 comments · Fixed by #82
Labels
enhancement New feature or request
Milestone
v1.0.0

Comments

@Breus
Copy link
Owner

Breus commented Mar 4, 2024

Basically: if no JsonPath is given as input, there is no need to track the current JsonPath at all. This would improve the performance in case no JsonPaths should be masked.
@Breus Breus added the enhancement New feature or request label Mar 4, 2024
@Breus Breus added this to the v1.0.0 milestone Mar 4, 2024
@gavlyukovskiy gavlyukovskiy mentioned this issue Mar 4, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.0.0
Development

Successfully merging a pull request may close this issue.

Avoid tracking JsonPath when there are no JsonPath keys Breus/json-masker
1 participant
@Breus