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.

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

Unexpected behaviour with inverse fieldmask #46

Open
will-isovalent opened this issue Jan 16, 2025 · 0 comments
Open

Unexpected behaviour with inverse fieldmask #46

will-isovalent opened this issue Jan 16, 2025 · 0 comments

Comments

@will-isovalent
Copy link

I noticed this behaviour when constructing an inverse fieldmask that I would consider to be unexpected. Suppose for example we have the following:

fieldmask_utils.MaskInverseFromPaths([]string{"a.b.c","a"}, func(s string) string { return s })

I would expect the resulting fieldmask to be a because the instruction to ignore the entirety of a should take precedence over the instruction to ignore a.b.c. Instead, we get a{b{c}}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant