-
Notifications
You must be signed in to change notification settings - Fork 1
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
Refine transfer data schema to classify transfer data derived from Unlock events #713
Conversation
Coverage Report •
|
app/model/db/idx_transfer.py
Outdated
class UnlockData(BaseModel): | ||
message: Literal[ | ||
"garnishment", | ||
"inheritance", | ||
"force_unlock", | ||
] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since there may be cases in the future where it is necessary to parse messages for events other than UnLock, I thought it would be better to use a structure name such as "DataMessage".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renamed the schema to DataMessage for future reusability d5509f1
4b35259
to
be9cfe6
Compare
be9cfe6
to
2327460
Compare
Close #700
DB
API
/{bond or share}/transfers/{token_address}
for searching by message field.Batch