Skip to content

Document alternatives for inheriting from robot class #676

@RealOrangeOne

Description

@RealOrangeOne

Teams will often try and subclass our robot to add their own functionality on top of it. Not only is it bad practice, but it can often conflict with the inner workings of our own classes.

Instead, teams should be encouraged to wrap our class. srobo/sr-robot3#21 prevents it, but there should be documentation of alternatives first.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions