Open Powersource opened 4 years ago
confirmed, I also recently got this behaviour :(
What do we want the actual behaviour to be?
What do we want the actual behaviour to be?
I like 'id', but whatever the docs say is fine with me.
I think being able to pay id or key in (but not both!) seems good
On Tue, 23 Jun 2020, 05:12 Christian Bundy, notifications@github.com wrote:
What do we want the actual behaviour to be?
I like 'id', but whatever the docs say is fine with me.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ssbc/ssb-db/issues/287#issuecomment-647654250, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUK3HUUTMQTZ36IJDFASBDRX6GGPANCNFSM4MRNHCNQ .
Sounds like we should just fix the docs then. :rocket:
No what I meant was it should accept either ID OR Key but throw an error if both are supplied!
On Tue, 30 Jun 2020, 03:39 Christian Bundy, notifications@github.com wrote:
Sounds like we should just fix the docs then. 🚀
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ssbc/ssb-db/issues/287#issuecomment-651200263, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUK3HQHNESMYTRJ2XW6NK3RZCYUHANCNFSM4MRNHCNQ .
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
(iIf you assign yourself ("I'm someone who wants this issue to stay open") then the bot will never touch it.)
Keep this open please
On Fri, 11 Dec 2020, 08:14 Christian Bundy, notifications@github.com wrote:
(iIf you assign yourself ("I'm someone who wants this issue to stay open") then the bot will never touch it.)
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ssbc/ssb-db/issues/287#issuecomment-742735468, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUK3HSCPPUH6D7IZA7X2R3SUEMZDANCNFSM4MRNHCNQ .
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This section says "If opts is passed, the message id is taken from either opts.id or opts.key" but when I test
that works, but
doesn't. I get this
If this is actually supposed to work, then when I skimmed the code it looked like this function came directly from flumedb so the bug might be there instead but I'm not sure.