Facebook-chat-api: When will there be a new package on NPM ?

[codeforequity-at]

I want to include the progress in my projects Testmybot and Botium, but the package on npmjs.org is rather old. I also don't want to point directly to the Git repository.
When will there be a new package released ?

[ravkr]

@Schmavery will probably release new version after merging #572, #612, #617 and maybe #603
But this is just my guess

[Schmavery]

That's the plan. @bsansouci and I worked on the weekend to try and get everything merged & unified a bit so that we can push a working version out to npm. We ran out of time in the end but hope to finish up tonight. Sorry for the delay, it can be hard to make time for this and there's quite a few fiddly details involved in making the datatypes line up and deciding how the format we expose should evolve as fb changes what they expose.

[ALiangLiang]

@Schmavery
Maybe you can use "pre-release" to keep the latest version? Also if someday FB api is changed, you can release many unstable hotfix version to prevent disaster.

https://medium.com/@mbostock/prereleases-and-npm-e778fc5e2420

btw. Using CI to automatic publish pre-release also a good idea,

[Schmavery]

Hey @ravkr, @ALiangLiang , we did our best to merge in the GraphQL versions of getThreadInfo and getThreadHistory in the dev branch tonight. If you have a chance, feel free to give them a try and see if there are any bugs we missed before we merge to master and publish to npm.

[ravkr]

@Schmavery I noticed that the new code contains ...Url in the returned objects but I think that we should call it ...URL (as we do with ID and not Id)

[Schmavery]

@ravkr I went with Url because that's how we've written it in the past.. hard to know with some of these things haha

As an update, we merged the dev bench to master and planning to publish soon.

[ravkr]

@Schmavery I thought that if we are changing so much to unify style, this could also be changed to match the style (and because URL is normally typed uppercase)

---

I don't think that prettier was a good choice
These new if statements and throws splitted to multiple lines are not looking good in my opinion :(

same here, why use 5 lines instead of just one? :/ Now I can display less code at once on my screen

[bsansouci]

@ravkr we don't want to spend time arguing about coding style here, there is so much other work to do. Thanks for expressing your opinion but we'll move forward with using Prettier and its default rules.

[Schmavery]

We published version 1.5.0 to npm today. Thanks for everyone's patience.