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

When searching for fungible-asset using searchAssets for particular owner_address, empty owner field in the response bug fixed #202

Conversation

AhzamAkhtar
Copy link
Collaborator

@AhzamAkhtar AhzamAkhtar commented Dec 29, 2024

Problem Description

  • When searching for fungible asset using searchAsset for particular owner_address, empty owner field in the response bug fixed

…ets, owner feild coming out to be empty bug fixed
@AhzamAkhtar AhzamAkhtar changed the title When searching for fungible asset using getAssetByOwner or searchAsset for particular owner_address, empty owner field bug fixed When searching for fungible-asset using searchAssets for particular owner_address, empty owner field in the response bug fixed Dec 29, 2024
Comment on lines +321 to +324
let token_account_data: Vec<token_accounts::Model> = token_accounts::Entity::find()
.filter(token_accounts::Column::Mint.is_in(asset_ids))
.all(conn)
.await?;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mints don't have owners they have mint authority so owner doesn't make sense on fungible assets. I think we should just keep this as null.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well this idea was inspired from helius, as in place of owner they also show the owner of the token-account for that corresponding fungible-asset which is being searched using searchAsset or getAssetByOwner for a given owner_address.
But happy to close this one.

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

Successfully merging this pull request may close these issues.

3 participants