Skip to content

Conversation

@smilingprogrammer
Copy link

Description

A simple example and doc for the feature Implemented in PR #217, for issue #123.

Related Issues

Type of Change

  • [BUG] - Bug fix (non-breaking change fixing an issue)
  • [ENH] - New feature (non-breaking change adding functionality)
  • [DOC] - Documentation changes
  • [MNT] - Maintenance

How was this solved?

Checklist

  • PR title includes appropriate tag: [BUG], [ENH], [DOC] or [MNT]
  • Linked to related issue (if applicable)
  • Code passes make check (lint, format, isort)
  • Tests added/updated for changes (if applicable)
  • Documentation updated (if applicable)

Testing

Additional Notes

NB: Was confused. Opened this new PR since it seems the project have been moved from SimonBlake/Hyperactive.

@SimonBlanke
Copy link
Collaborator

Hello @smilingprogrammer
please add these changes to the original PR: #217

It is custom to do so, because this way a maintainer has an easier job reviewing the new feature and to make sure the changes are all aligned.

@SimonBlanke SimonBlanke closed this Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants