Allow bypassing access checking (using serializer context)

Do we keep this feature request open indefinitely if nobody turns out to have a use case for this? Or do we mark it Closed (works as designed)? People can still find it when searching and then reopen it.

"Allow" cannot be followed immediately by an infinitive.

<3 language nitpicking. Thanks for helping me improve my English!

I don't have this specific problem, but I do have issues with cache management inside normalizers. Would this flag imply some new cache tag behavior?

I was always wondering whether the cache context could be used to put on additional cacheable metadata.

@damiankloip as described in my comment on #2575761-7: Discuss a better system for discovering and selecting normalizers, in a normalizer I am identifying additional entities to recursively normalize into a larger data structure.

My REST resource (using the standard EntityResource for Nodes) only has cache metadata for the originally requested node. Therefore, in order to address this all I can really do is customize the rest resource to add the list cache tag. I'd rather have the option to add cache tags for just those nodes I am adding.

#7: our normalizations are currently not cached at all. Only the actual responses are cached. So there is no risk of cache pollution.
#8: you're right, if were were to cache the results of our normalizations, we would have to add additional cache contexts. Or, rather, setting ingore_field_access would likely cause that caching to be disabled.

In more than two years, this was not once requested. I'm closing this.