Results 245 comments of Daniel

It previously didn't, but I've submitted a [PR](https://github.com/parse-community/node-markdown-spellcheck/pull/2) to make sure it does

Should be good for review @mtrezza

Sure, thanks for the bump - sorry I forgot about this

Can you add some detail around how masterKey should not be stored in code and used on trusted clients only

Of course, I've edited the original post to include some links. If you have any suggestions for topics that could be included in the section, please feel free to post...

Which approach do you think is best? It’s not a major issue so perhaps we can wait

I really can't work out why these tests are failing due to a new package-lock. The failing tests allow Parse Object to set updated objects `without` having to call .save...

Is this still an issue @mtrezza?

After some tedious investigation, It seems like the issue is caused by Parse Server. CI is currently locked to the latest version, yet `npm i` causes it to fetch `alpha`....

For those unfamiliar with VueJS, you can bind object properties and they are automatically updated by their respective component. ``` Name: {{object.name}} Save import { Parse } from 'parse'; export...