Skip to content

Examples/Demos #32

Open
Open
@hyperthunk

Description

@hyperthunk

We should have some of these. I suspect we will need to break up this repo into a multi-project repo.

We could then absorb other projects (like logging) that are related but not core to the library.

Should we just administer them at the top level, or use hit sub modules, or git subtree merging? I favour the latter, as it makes it easy to push back and forth, but perhaps just putting everything into a single repo is fine. I'd appreciate some reasoned opinions on this.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions