Daniel

@weblancaster only thing is, as soundcloud use multiple resolve steps to get the stream_url, it takes longer to load than the native api. But still beats nothing.

@skmbr I have a bit of a workaround for this, it's not ideal but seems to work (sorry I still use options API). ```js export default { props: ["modelValue", "position"],...

The full paragraph is here https://github.com/parse-community/parse-server/wiki/Parse-LiveQuery-Protocol-Specification#subscribe-message I assume that the functionality of _"if you are only interested in the change of the name field"_ is different to the existing functionality...

Actually what do you think of: `query.whereChanged(...keys)` `query.changed(...)` `query.triggerFields(...)` `query.listen(...)` `query.restrict(...)` `query.selected(...)` `query.alter(...)`

Just need to get tests to pass

Sounds good to me. We can easily drop in the amendment from https://github.com/parse-community/minami/pull/1#issuecomment-1140267604

The same template will need to be applied to the JS repo too

There were [some changes](https://github.com/nijikokun/minami/commit/68fd18c073e9d9008899c17d0f9d9043af834a40) to the template which may have been the reason why there is a fork. The main changes seem to be to add `@interface` to the nav...

I can confirm that I have written a test that fails on `alpha` but passes on this branch. I have provided it in my review. Could you please also link...

Looks mostly good - might just have to fix lint and tests