Skip to content

Docs: Move code snippets into dedicated python files add formatting and linting, fixing any outstanding errors #1064

Closed
@michaelbrewer

Description

@michaelbrewer

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

In the past there was many documentation errors found like #1004 , on a regular basis i would try to help the
community by verifying the code examples, that they can compile, linted, valid formatting and had the correct line highlights

As part of general papercuts #857 and then later #1009 it was decided to split up the examples into separate files so that they can be linted or validates.

Currently the AWS Lambda Documentation has many typos, syntax errors, missing imports, invalid yaml indentation and terraform errors (about 25 errors currently and we keeping on running into this errors each time code examples are updated or added (see #1004). Here is a list of some of them as separate issues:

Hosted version of this is at: https://gyft.github.io/aws-lambda-powertools-python/latest/

Describe alternatives you've considered

Keeping the examples inside the markdown docs. But we run into issues like below, where errors are not easily picked up

Additional context

As a side effect many existing errors will be resolved AND measures put in to prevent them from happening again. Here is a list of errors currently in the documentation

List of open pull requests

Originally part of a simple PR #1065 but now split up into smaller ones

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions