Cristiano Betta

I agree with most what's being said here. Let's focus on the real usecase here though, and not solutions. Often solutions are simple once you properly understand the usecase. So,...

@sammachin thanks for clarifying. So @leggetter what really is the use case? Can you help describe it a bit more structured?

Changes to be made: - [ ] Update config loading to check BOTH local and global `.nexmorc`. This way we could have API keys in `~/.nexmorc` and host settings in...

Remaining questions: * Currently `nexmo setup` writes to a global file, and `nexmo setup --local` to a local file. This would be opposite to `nexmo config:set` as proposed. * What...

Awesome. Any idea why the spec says you can't use them for identifying purposes? Seems pretty accurate to me from some of the tests I ran.

I think I built my own @marvinkome. Sorry, not very useful.

I think the project I was working on got abandoned. Instead I just created my own flow from scratch with React for another provider recently.

Tnx for the update after 6 years 😂

Ah, good point. I think the answer is "both and more". This tool isn't really specific to either and instead can be used to validate any fields in an object...

Sure. As for the name: I based the name on @mheap's original project. Maybe we should change the name if we know it will get merged in with a new...