Right but for the docs to be updated would require someone pushing a new package version to Hex?
Also the top of every source code file says not to touch it because it’s machine generated, example:
# WARNING: DO NOT EDIT, AUTO-GENERATED CODE!
# See https://github.com/aws-beam/aws-codegen for more details.
If the docs are generated by code comments but the files that contain the code are read-only, I can’t think of a way to open a PR on that. The changes would get lost.
This is what I normally do, but yeah
aws-elixir has no tests. At least none that show how to use the functions that this library exposes.
In the end this leaves us with no to limited docs, no test suite and no way to update the docs due to things being auto-generated. How would we proceed to improve this given the above constraints? It sounds like an expert would need to crawl through the popular AWS services and write custom guides / docs and then publish them to somewhere outside of the code repo?
But even that isn’t a great experience because it could hard to find and could very easily become outdated vs what’s available in the library.