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

[2.6][T4] type of lockTransactionId in transaction schemas #3245

Closed
dated opened this issue Nov 11, 2019 · 2 comments
Closed

[2.6][T4] type of lockTransactionId in transaction schemas #3245

dated opened this issue Nov 11, 2019 · 2 comments

Comments

@dated
Copy link
Contributor

dated commented Nov 11, 2019

lockTransactionId is defined as follows in the transaction schemas:

lockTransactionId: { allOf: [{ minLength: 64, maxLength: 64 }, { $ref: "hex" }] },

lockTransactionId: { allOf: [{ minLength: 64, maxLength: 64 }, { $ref: "hex" }] },

Since lockTransactionId is a reference to a transaction id, the respective types should be the same. Strictly speaking this is currently not the case, with hex being a subset of alphanumeric.

transactionId: {
$id: "transactionId",
allOf: [{ minLength: 64, maxLength: 64 }, { $ref: "alphanumeric" }],
},

lockTransactionId should be defined as

lockTransactionId: { $ref: "transactionId" }

Also, wouldn't hex instead of alphanumeric suffice as a constraint on transactionId?

@ghost
Copy link

ghost commented Nov 11, 2019

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

@faustbrian faustbrian changed the title type of lockTransactionId in transaction schemas [2.6][T4] type of lockTransactionId in transaction schemas Nov 12, 2019
@ghost
Copy link

ghost commented Nov 12, 2019

This issue has been closed. If you wish to re-open it please provide additional information.

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

2 participants