Thanks to visit codestin.com
Credit goes to github.com

Skip to content

more than one example #46

@gpx1000

Description

@gpx1000

The example section is almost more of an integration test than it is sample / example code meant for humans. Most packages come with more than one example use case. I'm wondering if it makes sense to do one of two or both things:
1.) make this integration test / sanity check as the user story (what it currently is).
2.) allow for more than one entry in the examples or even packaged zip files complete with common build project files.

I think this is an issue as the developer that's consuming the package shouldn't have a need for downloading the original package to make heads or tails of it (get docs and sample code in same distribution rather a separated task).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions