Add support for custom registration fields

[AlMcKinlay]

Fixes #431

This allows the client to specify fields that will be sent with the registration, and then passes all of them to the server register emit.

I couldn't see any existing appropriate tests for these, and didn't have time to make any from scratch today.

[sonnyp]

Unfortunately I don't accept non security related PR for node-xmpp-client as its architecture doesn't allow for growth.

There's a rewrite in progress that addresses this issue though and we even have a registration plugin but it needs to be updated. I'll do that ASAP and I'll keep your use case in mind. I'll let you know on #431

[AlMcKinlay]

AFAICS, the rewrite isn't ready for production, is that correct?

…

On Mon, 19 Jun 2017, 20:26 Sonny Piers, ***@***.***> wrote: Unfortunately I don't accept non security related PR for node-xmpp-client as its architecture doesn't allow for growth. There's a rewrite in progress that addresses this issue though and we even have a registration plugin but it needs to be updated. I'll do that ASAP and I'll keep your use case in mind. I'll let you know on #431 <#431> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#432 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACD_4S7ZpnWBR_1fhA8yEg0AnuRgx-hbks5sFstSgaJpZM4N-ZXn> .

[sonnyp]

@YaManicKill that's correct meanwhile I recommend you keep using your fork. The rewrite provides a different API so you might wanna keep that in mind.

[AlMcKinlay]

Alright, well thanks anyway, @sonnyp

[sonnyp]

see #783