Daniel

Yes, that sounds good to me

I solved this in my projects using `npm i events`, however it results in the production build with vite failing. The error was: `TypeError: (0 , _decode2.default) is not a...

This isn't breaking and does not change the `fields` behavour (although perhaps `fields` should be renamed to `select` for consistency). `fields`: behaves as `select`, defines what fields to return `listen`:...

Yes, I agree. The issue of renaming `.fields` to `.select` and deprecating `.select` is a different issue to this PR though - this PR introduces a new feature `listen` that...

Yep! We will just need to update the spec accordingly - describe `fields` as restricting fields, and `listen` to the current explanation for `fields`

Can this be merged in to PS6 as a breaking change @mtrezza? Some refactoring will be needed

It's a breaking change - previously I had it as a server parameter but now it's change in default behaviour

The whole point of removing the obscurity was that you can check whether a user exists by calling `.signup` https://github.com/parse-community/parse-server/security/advisories/GHSA-cfgm-jqhh-xmhr#advisory-comment-64808

Closed via #8293

@cbaker6 I'm thinking that too. Perhaps the spec was built before the feature was built, and it ended up behaving the same as `select`. So I suppose this issue is...