Skip to content

Connections class design & metadata options #16

@willGraham01

Description

@willGraham01

The Connections object is likely going to get a bit bloated, since all our central functionality will revolve around it. That in itself can't really be helped, but we might want to think of ways we can divide up the code into sensible chunks.

That being said, there are some more important considerations we should give to this class:

  • We should provide an option for storing metadata about the connectivity information in the class itself. We'll also need an appropriate attribute for this too.
  • The name Connections might not be the best we can do to describe what the class actually does.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No 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