[BUG] "personal information not registered" flag is set incorrectly with latest_flg == 1 when the data was set null - Githubissues

BoostryJP / ibet-Prime

Advanced API Toolkit for Digital Securities Issuance and Management on the ibet Network 🚀

https://ibet.jp/ibet-for-fin

Apache License 2.0

11 stars 1 forks source link

[BUG] "personal information not registered" flag is set incorrectly with latest_flg == 1 when the data was set null #640

Closed purplesmoke05 closed 4 months ago

purplesmoke05 commented 4 months ago

Describe the bug

GET: /{token_address}/history/{ledger_id} returns some_personal_info_not_registered flag and it may be set incorrectly when the personal info was modified to null by the issuer.
This is because there are some differences of the below two.

https://github.com/BoostryJP/ibet-Prime/blob/9fc0812de645f5f47c2b13bd4beda27b3945e60c/app/utils/ledger_utils.py#L330-L345

https://github.com/BoostryJP/ibet-Prime/blob/9fc0812de645f5f47c2b13bd4beda27b3945e60c/app/routers/ledger.py#L966-L975

Expected behavior

"personal information not registered" flag is set correctly