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

V03 issue617 (part of it.) "topic" depends more on payload format, than message protocol. #685

Merged
merged 4 commits into from
May 25, 2023

Conversation

petersilva
Copy link
Contributor

move topic generation away from message protocols and into the payload format code.
the WIS format has a different scheme for determining topic hierarchy, so need a way for the postformat/wis.py to return the "topic" for published messages.

I think the universal idea is that one should be able to determina an appropriate topic from the content of the message.

@petersilva petersilva changed the title V03 issue617 V03 issue617 (part of it.) "topic" depends more on payload format, than message protocol. May 24, 2023
@petersilva
Copy link
Contributor Author

petersilva commented May 24, 2023

last patch fixes the breakage at in the publish API ( #681 )

@andreleblanc11
Copy link
Member

Looks good. Do we all need to approve the pull request for it to merge?

@petersilva
Copy link
Contributor Author

hey @andreleblanc11 it looks like you have not approved it.. you just put a note in it...
that's a good question... how much review is enough, and what a reviewer should do...
I was just going on if one person reviewed it then that was good enough... but it doesn't show you reviewed it... so I'm still waiting... I think you could also "rebase and merge" which is the kind of approval that just makes it go... or you can leave that to me... but some kind of approval would be good.

@andreleblanc11 andreleblanc11 merged commit a527e83 into v03_wip May 25, 2023
@andreleblanc11
Copy link
Member

andreleblanc11 commented May 25, 2023

I think one reviewer is probably enough. We are all so busy with other stuff that having all of us review every time would be a hassle lol. As for what the reviewer should do.. that is a good question. Maybe there should be some sort of standard to be set? (check the commits, insert appropriate comments, etc.). We can add it to the agenda for the next dev meeting

@petersilva petersilva deleted the v03_issue617 branch May 27, 2023 18:49
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