Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameterized messages in PyRFLX #743

Closed
treiher opened this issue Aug 17, 2021 · 0 comments · Fixed by #778
Closed

Parameterized messages in PyRFLX #743

treiher opened this issue Aug 17, 2021 · 0 comments · Fixed by #778
Assignees
Labels
pyrflx Related to pyrflx package (Legacy Python API)

Comments

@treiher
Copy link
Collaborator

treiher commented Aug 17, 2021

Add support for parameterized messages (cf. #609) to PyRFLX.

@treiher treiher added the pyrflx Related to pyrflx package (Legacy Python API) label Aug 17, 2021
@treiher treiher added this to To do in RecordFlux 0.6 via automation Aug 17, 2021
@jklmnn jklmnn self-assigned this Sep 21, 2021
@senier senier moved this from To do to In progress in RecordFlux 0.6 Sep 21, 2021
jklmnn added a commit that referenced this issue Sep 21, 2021
jklmnn added a commit that referenced this issue Sep 21, 2021
jklmnn added a commit that referenced this issue Sep 22, 2021
jklmnn added a commit that referenced this issue Sep 22, 2021
@treiher treiher linked a pull request Sep 27, 2021 that will close this issue
@treiher treiher moved this from In progress to Under review in RecordFlux 0.6 Sep 27, 2021
jklmnn added a commit that referenced this issue Sep 28, 2021
jklmnn added a commit that referenced this issue Sep 28, 2021
RecordFlux 0.6 automation moved this from Under review to Merged Sep 28, 2021
jklmnn added a commit that referenced this issue Sep 28, 2021
jklmnn added a commit that referenced this issue Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pyrflx Related to pyrflx package (Legacy Python API)
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants