Proposal/RFC: split up the API and the server about postgres-meta

[w3b6x9]

@soedirgo

TypeScript supports function overloading

This reminds me of Elixir's function arity. Very cool!

[soedirgo]

I'm done refactoring the API to use the functions above (really liking retrieve, and TypeScript supports function overloading apparently).

I'll try to finish this off tonight and run it through you tomorrow during cafe day. Sorry this took a while!

[soedirgo]

Interesting, I suppose the API can be safely split off since the server is just for serving requests.

For making requests from the CLI, we can probably use openapi-generator as @steve-chavez recommended here. Also, do we plan to use Node/TypeScript for the CLI?

[kiwicopple]

do we plan to use Node/TypeScript for the CLI?

Yeah I had a play with Gluegun on the weekend and it seems like it could do the job. TBD though - I have only experimented with some small use-cases (generating TypeScript models/entities from the database).

[kiwicopple]

We have started this process here: #87

And @soedirgo has outlined how it might look eventually here: https://github.com/soedirgo/postgres-meta

One thought: we have several functions like getAll(), getById(), getByName() etc. How would you feel about creating a common interface, where the params determine the private function:

• list()
• retrieve(params) - For example, takes one of: { id?: number, name?: string }
• create()
• update()
• remove()

[github-actions]

🎉 This issue has been resolved in version 0.15.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀