We should register the npm @libretime namespace.

I think we should compile 2 different targets, both es5 and es6 so we have a dist for older browser, and use the es6 dist for the web app (vue) that will recompile the library anyway.

The test suite for each client needs populating to actually test things

Hi there. I am the author of the openapi-generator python client which has now moved to https://github.com/openapi-json-schema-tools/openapi-json-schema-generator
Your repo uses this client.
I want to make sure that I understand what is important to the end users of the python client. If you have some time can you provide some feedback on what features you value in the generator, any pain points, and what you would like improved?
If you could provide your feedback here it would help with future improvements. Thank you!

I'm not sure what we want here. Do we want a push to main on schema update or do we want it to push to a branch and open a PR against main for any changes?

The PR approach is easier to audit, but does add complexity in how those PRs are managed.

The java script package should not be libre_time_api. It seems to ignore the parameters set in the github actions workflow.

The commit message from the CI are not following the conventional commit format.

To make it consistent with our generated packages names, we should rename the repository to client.

Many packages names needs fixing and should follow our naming convention.

The python module should not be libretime.api.
The java script package should not belibre_time_api.

The install command assumes that the client is in the root of the repo. This needs to be updated to point to the python-client sub-directory.

pip install -e "git+https://github.com/libretime/api-client.git#egg=libretime_client&subdirectory=python-client"

https://github.com/libretime/api-client/blob/main/python-client/README.md?plain=1#L20

The old files are not removed when the generator update a client. See the python client directory.