Noah Silas

One thing I'm noticing as I've been pushing patches on to this branch to make the tests all pass is that the traversal stuff is actually quite complex. I'm thinking...

The concern is that two replacers might be going at once, and since they rebuild the tree with their modifications, one might clobber the other. But, thinking about it with...

I took a stab at replacing the traversal stuff, and that looks like this: https://github.com/Hustle/parse-server/commit/6bbae2842c0e0d13b519c9c82779d303fa5b96a1?w=1 It's definitely tricky, but I could follow up separately to simplify that, and it makes...

Sorry for the long delay here! I've updated this PR to reflect the "minimal" branch I had linked to above, and I'll submit a separate PR relating to the traversal...

@omairvaiyani I took a stab at rewriting the commits in this PR on top of master to remove all of the auto-formatting noise. Does https://github.com/Hustle/parse-server/commits/omairvaiyani/improve-auth-efficiency look like it captures your...

I'm not sure what the best strategy here would be. It seems like this should be functionally part of [HtmlToPlainText#convert_to_text](https://github.com/premailer/premailer/blob/master/lib/premailer/html_to_plain_text.rb), but this operation seems like it would be better performed...

Oof, I realized that nested objects added via `include` also need to have their special fields (id, createdAt, ...) projected out too. 😩

We should consider bundling this with #7760 and adding multiple new search parameters in a single release.

@rahul A couple questions as I'm working on a prototype: - How do you feel about requiring a Timezone extension on Schedule resources that define availability? To me this seems...

> > How do you feel about requiring a Timezone extension on Schedule resources that define availability? To me this seems like it removes one potential source of ambiguity, but...