Proposal for V1

[phr3nzy]

Here's what I think can add a lot of value quickly:

• Refactoring types: replacing type with interface and using Generics where it fits
• Setting up Linter and Formatter
• Automating dependency updates, testing and release with actions
• Support esm and commonjs exports

[rod-anami-kyndryl]

@phr3nzy let's create pattern for the first item. I want to tag it for 0.5.0 as we're changing the interfaces.

[Intevel]

@rod4n4m1 What about migrating this complete project to TypeScript?

[phr3nzy]

@rod4n4m1 Sorry for my absence but civil war broke out and I'm trying to get out. Will get back to this when I make it out alive hopefully.

[rod-anami-kyndryl]

@phr3nzy Stay safe! I'll pray for you.

[rod-anami-kyndryl]

@Intevel Probably we will need to do that, but right now I want to make sure we have a working package.

[shanegenschaw]

@rod4n4m1 What about migrating this complete project to TypeScript?

I am interested in this idea and may have some time in the short-term to pitch in, if contributions are welcome.

Some additional ideas or topics of discussion:

• The typescript typings need fixing. While all efforts are commendable and appreciated, the current typings on this repo are pretty broken and caused me to look elsewhere, or actually start "growing my own", yet another vault client library. I'd rather contribute to this one, and continue to make it better. It seems to be one of the more robust, fully featured, and actively maintained packages available in the community. I'd rather help to get this package to "all in typescript", if that aligns with the package owner's vision and long-term plans, of course.
• code generation of types/interfaces/operations using openapi-typescript and Vault's openapi spec. The Vault API spec can be generated with something like:

  curl --request GET \
    --url http://127.0.0.1:8200/v1/sys/internal/specs/openapi \
    --header 'X-Vault-Token: ***

  This could be automated in the github workflows and tracked against the latest Vault openapi schema with a docker-compose setup or something similar.
• Building upon on the point above, use of openapi-fetch to enable exporting typed API operations and request/response data structures.

@phr3nzy stay safe, you are in the thoughts of myself and several of my colleagues I've shared this thread with ❤️

[rod-anami-kyndryl]

@shanegenschaw This is an excellent idea and approach!

Definitely we can use it for this project for 0.5.0.

I'd like to fix what we have today before we move to the next major release. Can you show me how we would fix one case of type/interface with this model?

I can do the heavy lift after we agree on a model of type/interface for 0.4.14.

Thanks