Wrap paddle actions with DB transactions

[aerosol]

Changes

This change makes all the paddle webhook updates transactional.
I considered rewriting it to Ecto.Multi-based services but that can be made on top of this in another iteration, since shipping the change itself feels quite critical.

Tests

• Automated tests have been added
• This PR does not require tests

Changelog

• Entry has been added to changelog
• This PR does not make a user-facing change

Documentation

• Docs have been updated
• This change does not need a documentation update

Dark mode

• The UI has been tested both in dark and light mode
• This PR does not change the UI

[vinibrsl]

Good one! And I agree that moving to Ecto.Multi is a good idea and we should do it in a separate release.

[bundlemon]

BundleMon

Unchanged files (7)

Status	Path	Size	Limits
✅	static/css/app.css	515.19KB	-
✅	static/js/dashboard.js	297.45KB	-
✅	static/js/app.js	12.13KB	-
✅	static/js/embed.host.js	5.58KB	-
✅	static/js/embed.content.js	5.06KB	-
✅	tracker/js/plausible.js	748B	-
✅	static/js/applyTheme.js	314B	-

No change in files bundle size

Final result: ✅

View report in BundleMon website ➡️

---

Current branch size history | Target branch size history

[aerosol]

@vinibrsl made the errors bubble up so it rolls back this time

[ukutaht]

Looks good!

Is there any benefit between Ecto.Multi vs Repo.transaction? If I understand right it's just cosmetic / style difference or is there more to it?

[aerosol]

Is there any benefit between Ecto.Multi vs Repo.transaction? If I understand right it's just cosmetic / style difference or is there more to it?

Repo.transaction accepts Ecto.Multi structs. The way I see it there's testability benefit - you can test some aspects without having to provision the DB; sometimes all you care about is whether the transaction structure/context has been built valid, not whether the database works. You also get better insight into failures, the failing step is explicitly named & returned. It makes it simpler to mock (or skip) certain transaction steps if need be. You can compose multiple Multis 😈 together with little to no effort - this supports building "service oriented" code bases.