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

v1.1 query.read gives objects with only the { value: { ... } } part #1

Open
ameba23 opened this issue Nov 18, 2019 · 0 comments
Open

Comments

@ameba23
Copy link

ameba23 commented Nov 18, 2019

sorry if the problem is not so clearly described:

im getting some inconsistant behaviour between kappa-view-pull-query v 1.0 and 1.1. Perhaps the behaviour is intentional.

when doing: core.api.query.read({ query, opts })

v1.0 queries give me the complete objects: { key: 'deadbeef', seq: 4, value: { content: 'of the message' } }
but v1.1 queries are giving me objects with only { value: {... } }, without the { key: ..., seq: n ... part. so i cant work out who authored them from the queries.


im using v1.1here: https://gitlab.com/dark-crystal/kappa-bls-sign/blob/master/index.js

and 1.0 here: https://github.com/ameba23/metadb/blob/master/index.js

but its difficult to say for sure if this module is causing the problem, because if i try to downgrade to 1.0 in the kappa-bls-sign module, stuff breaks.

upgrading metadb from 1.0 to 1.1 does indeed mean that the queries only contain the value properties.

but these two modules are using different versions of kappa-core (4.0.1 and 3.0.2 respectively) so its hard to know what is causing what.

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

No branches or pull requests

1 participant