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

api.derive.accounts.identity called with SuperIdentity doesn't return SubIdentities #5810

Open
3 of 10 tasks
wpank opened this issue Mar 7, 2024 · 1 comment
Open
3 of 10 tasks
Labels
P4 - Needs Investigation Requires analysis to determine cause or feasibility. Not fully understood, needs research first.

Comments

@wpank
Copy link

wpank commented Mar 7, 2024

  • I'm submitting a ...
  • Bug report
  • Feature request
  • Support request
  • Other
  • What is the current behavior and expected behavior?

Calling api.derive.accounts.identity gives some slightly unexpected behaviour - when called with the super / parent identity, it doesn't return the sub accounts, although calling with with one of the sub identities it returns the full thing, with all the sub identities / parent account. I want to say it used to be the case that this call returned sub-identities

https://github.com/w3f/1k-validators-be/blob/master/packages/common/src/chaindata/queries/Identity.ts#L91

This is how the call is being used in the 1kv-backend - I needed to add in the additional sub identity query.

  • Please tell us about your environment:
  • Version:

  • Environment:

    • Node.js
    • Browser
    • Other (limited support for other environments)
  • Language:

    • JavaScript
    • TypeScript (include tsc --version)
    • Other
@TarikGul
Copy link
Member

TarikGul commented Mar 7, 2024

I did just add some small compatibility fixes with api.derive.accounts.identity when increasing the substrate metadata to the latest release (This will be included in next weeks release), but I need to see if there is any correlation or what the root of the issue is.

@TarikGul TarikGul moved this to Issues (Bugs) in Polkadot-js general project board Mar 8, 2024
@TarikGul TarikGul added the P3 - Low Non-essential improvements or minor fixes. Can be scheduled flexibly as time permits. label Oct 29, 2024
@TarikGul TarikGul moved this from Issues (Bugs) to P3 - Low in Polkadot-js general project board Oct 29, 2024
@TarikGul TarikGul moved this from P3 - Low to P4 - Needs Investigation in Polkadot-js general project board Oct 30, 2024
@TarikGul TarikGul added P4 - Needs Investigation Requires analysis to determine cause or feasibility. Not fully understood, needs research first. and removed needs investigation P3 - Low Non-essential improvements or minor fixes. Can be scheduled flexibly as time permits. labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 - Needs Investigation Requires analysis to determine cause or feasibility. Not fully understood, needs research first.
Projects
Status: P4 - Needs Investigation
Development

No branches or pull requests

2 participants