Announcement: tripletexjs v3 🎉

[simenandre]

Hello 👋

My name is Simen. I am the maintainer of Tripletexjs. I've built this SDK mainly to make it easier to make integrations with Tripletex. The SDK was built in 2016, based on Swagger Codegenerator. It became somewhat neglected, but still widely used internally for many of our projects. We opened a ticket in March of 2020 with the agenda of refactoring the whole library, to ensure that we utilize modern programming principles (and hopefully fix some the issues that we've had over the years). This began with migrating to OpenAPI Generator, since Tripletex had changed their swagger.json file a lot, we had a lot of issues. Still having issues with OpenAPI Generator, we moved on to another library in November 2020. Still, we learned more, and have ended up with a much more stable approach with Runtypes and typical-fetch. The drawback is that there is no longer any code generator.

In other words, please welcome v3. 🎉 It is not production-ready, and there is stuff that we've learned over the years using tripletexjs that we want to add. For now, we want to welcome users to test and give feedback on the new codebase. You can track the development on the next-branch.

Most notable changes

• New and improved API
• Much more helpers (using native JS types, e.g. Date)

Object-arguments

Before, we had ugly functions like this:

const res = await customers.search(undefined, undefined, undefined, undefined, '123456789');

We are now able to do this:

const client = new TripletexClient();
const res = await client.employee.list();

Want to help?

We want to help users utilize this library to create awesome integrations with Tripletex. We are planning to create tutorials and migration guide from v2 to v3. Open a ticket if you want to help!

[simenandre]

By this point, I'd say that v3 has become stable, and we can start to outline the potential changes we'd love to see for v4.
I've opened an issue related to v4 here: #59

I will soon make a dependency update for everything before cutting a new SDK release without the next tag. We at that point merge next into main and delete the next branch, opening up next for potential v4 work.