Split & change API?

[dagnelies]

I was thinking of doing some refactoring and breaking changes. Basically two things:

• using terminology like createKeyPair() and authWithKey() instead of register/login to be closer to the meaning of what actually happens
• split the module in three parts: client, server and parsers. The intent behind it is that clients usually only require the first, except the demo which requires all or for debugging purposes, while the server only require the verifying part.

As a result, the renaming/splitting the current webauthn lib as follows:

client.createKeyPair()   // same as current "register"
      .authWithKey()   // same as current "login"
server.verifyCreate(payload, expected)  // returns parsed payload
      .verifyAuth(payload, expected)   // returns parsed payload
parsers.parseCreate()
       .parseAuth()
       .parse*

What do you think @mattmazzola ?

[dagnelies]

Also, I would swap the word "external" in favor of "roaming"