Brandon Slinkard

Unlikely unless you tackle it on your own. The primary vorpal repo is basically unmaintained at this point. There is a “reforge” that’s going on here: https://github.com/vorpaljs-reforged/vorpal if you’re interested

I simply haven’t had time to contribute to the reforge efforts recently. We need more hands but the org is set up and I think we’re definitely willing to get...

Do you need help getting this fork rolling? I'd be glad to hop on board with it as well. I've noticed the [Vorpal Gitter](https://gitter.im/dthree/vorpal) is pretty active and we could...

Yep and so anyone reading this doesn’t think we’re splitting the effort unintentionally, we’ve pulled in Ore’s work into that org for now while we work. This gives us proper...

@tsujp Because the project is dead and the old vorpal admins haven’t put anyone else in charge.

Thanks for looking into this @abramenal, is there anything we can do to help? I just started running into this as well. I'm happy to investigate it a bit but...

I did this in my project by adding a `data-contracts.eta` template and overwriting the default dataContractTemplates object with this: ```ts const dataContractTemplates = { enum: (contract) => { return `enum...

+1

@icebob and @ngraef what are your thoughts on simply logging a warning statement if a version like "5" is used? That way we can preserve the existing functionality but potentially...

I ran into this as well, after digging around through docs for a while the fix was actually pretty simple, I was mistakenly using the [client config](https://www.apollographql.com/docs/devtools/apollo-config/#clientservice) structure when I...