vulcan-users - permissions - filter out array based fields #2056
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.
When using the resolver for the resolveAs examples from the documentation:
http://docs.vulcanjs.org/field-resolvers.html
I found that the Users.getViewableFields helper was return array based field names, which obviously are not compatible with the selector/options objects passed through to collection.findOne.
I did a search to see where the function is called in the DEVEL codebase and see that it is used only once. That being said, others may well be using it and require the array field names, so perhaps might help to create a wrapper function that strips them out to use instead, but for now I figured I would submit this for you.