Skip to content

Think about board configuration structure... #4

@metasoarous

Description

@metasoarous

Should it all really just live in one map? Should we have protocol methods that get certain important things so implementors have a clearer sense of what they need to do? Or just document what things should be there and what shouldn't? Has implications for #3, as well as the simulator implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions