Initial set of auto-generated error pages for review and to kickstart the iterative improvement cycle #2790
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the ably-os errors tooling, these documentation pages are all auto-generated. These pages need review, and iterations will be needed in the ably-os CLI tool to improve them. This initial set is up here for review so that we can start the process of improving them until they are good enough to publish.
Note this set of error pages is not complete (40011, 40012, 40013, 40014, 40015, 40017, 40018, 40019, 40020, 40022, 40023, 40024, 40030, 40031, 40032, 40099, 40100, 40101, 40102, 40103, 40104, 40106, 40113, 40115, 40121, 40130, 40131, 40132, 90099, 91000, 91001, 91004, 91005, 91100, 92000, 92001, 92002, 92003, 92004, 92005, 92100, 93001, 93002 are missing), but that is not relevant at this stage as we have enough to start reviewing.To get to this point, there are numerous previous steps:
generate-repo-overview
-> Generate repository overview with architecture analysis for each repogenerate-repo-error-reports
-> Generate detailed error reports with contextual data (function context, trigger conditions, user actions, recovery paths)generate-error-code-research
-> Generate comprehensive error code research from our internal code, SDK code, tickets, conversations in Slack, calls, internal documentation.