Support fullTextSearch in 1.11.0

[srameshr]

Here is a thread discussing it.
#541

[montymxb]

Thanks, and we would probably be looking at 1.12.0 for the new features.

Speaking of new features #367 is just about done, just rerunning CI before we give it a final look. If that get merged we'll probably put that in as well.

[srameshr]

Yes, please.
And please remember to update parse, the JS-SDK version for the parse-server dependencies.
Thanks for your prompt reply. Hope this gets done by the end of this week.

[montymxb]

Definitely, when we do put a release out for the JS sdk, and if we don't get to the parse-server parse dependency, notify us with an issue/pr. We're bouncing around among all the notifications for the server & various sdks, helps to let us know if we need to get back to something 👍 .

[flovilmart]

We could also be a bit less aggressive on parse server with the semver or our maintained dependencies, this would
decouple the releases of parse-server and the JS SDK

[srameshr]

@montymxb Any updates on this?

[montymxb]

Yeah, #367 was merged not too long ago. I need to double check that there isn't anything else outstanding. Probably Thursday or this weekend.

…

On Mon, Feb 5, 2018, 09:12 Siddharth Ramesh ***@***.***> wrote: @montymxb <https://github.com/montymxb> Any updates on this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#548 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE1d4K_YVBpDPvEa2DwqVRQaWkF_a7RGks5tRzZrgaJpZM4R2Ls9> .

[flovilmart]

@srameshr this is not how it works, nobody is paid to run this open source project, if you’re in a hurry, you can always fork the project(s) and use intermediate versions.

[srameshr]

@flovilmart I did it. The problem is, when uploaded to AWS EBS, the package.json with the link to github forked project never picks up at all. I tried few things to but to no avail.
I just don't want to fork and create an actual npm package of the fork to make EBS run.
I don't mean to push anybody.

[montymxb]

It's alright. Just try to understand that, being a community, we all have commitments besides what we do for parse. We will put out a release, but it will be when we are ready and when we are able. Not trying to backlog things or put this aside, but it's not the only thing on our plates right now.

…

On Tue, Feb 6, 2018, 09:17 Siddharth Ramesh ***@***.***> wrote: @flovilmart <https://github.com/flovilmart> I did it. The problem is, when uploaded to AWS EBS, the package.json with the link to github forked project never picks up at all. I tried few things to but to no avail. I just don't want to fork and create an actual npm package of the fork to make EBS run. I don't mean to push anybody. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#548 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE1d4D0yIviNL_Fr9kXnHa-XpJ865kx9ks5tSIk1gaJpZM4R2Ls9> .

[srameshr]

@montymxb

[srameshr]

You guys should be so proud of yourselves.
Well done.

[montymxb]

@srameshr not sure why you closed this. Although we haven't been able to address as soon as you may have liked this is still a relevant issue. It should remain open until resolved.

We're not ignoring this, if that's your perception. The simple answer is that we do not have the time to address this currently. When we get time, and when we get to this issue, we'll take care of it.