Skip to content

Make implementing a new pyborg module simpler #93

@jrabbit

Description

@jrabbit

We should make the commands registry pattern eas(ier) to copy into new modules.
We could provide learn/reply methods via a baseclass with inherent settings handling? (attrs might get mad check there)

Document the procedure? Only confusing thing right now is where they go and where to register them in the entrypoint I think? If something else is confusing please ask.

Metadata

Metadata

Assignees

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions