-
Notifications
You must be signed in to change notification settings - Fork 51
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
'descending #317
Comments
A recent commit changed the Store.scan and Session.fetchAll JavaScript APIs so that the new 'descending' field is now required. Was this planned, or by mistake? Shouldn't we just have a default like there is for the other options. |
@ff137 — I’m guessing that was a change you made? ^^^^ |
@scottexton the relevant changes were made here: https://github.com/hyperledger/aries-askar/pull/291/files My intention was for the new fields to be optional / have defaults, so that there are no breaking changes. I think I managed that in the rust/python code, but not in the JavaScript wrapper... apologies. Looks like |
@ff137 Will you make a fix for that, or do you want me to? |
@scottexton I do feel responsible to clean up my mess and make a PR, but review-approve takes time. It's probably best if you can test a fix, given that you're working with the js wrapper. Should just involve adding a ? to those |
@ff137 Alright. I will include a fix in amongst my other changes. |
A pull request has been created with a fix for this issue (#319) - this fix is embedded within a larger change to introduce ODBC backend support. |
No description provided.
The text was updated successfully, but these errors were encountered: