can't to recognize api type annotations for different chain at one project

[cinlk]

We have two substrate chain with different metadata, and generate each of their const, query and tx api in same declare (same namespace) module. there are two same name storage method with different parameter type.
for example chainA has this storage method definition as follow:

balance:{
    storageVersion: AugmentedQuery<ApiType, () => Observable<**ChainAType**>, []> & QueryableStorageEntry<ApiType, []>;
}

chainB storage method definition as follow:

balance: {
      storageVersion: AugmentedQuery<ApiType, () => Observable<**ChainBType**>, []> & QueryableStorageEntry<ApiType, []>;

}

When I want to use both of their api in one project and set the tsconfig.json to apply 2 different api augmentations.

"paths": {
    "@polkadot/api-augment": [
      "./node_modules/@substrate/api-augment/chainA/index.d.ts",
     "./node_modules/@substrate/api-augment/chainB/index.d.ts"
     ],
} 

Initialing api with chainB provider find that the "api.qeury.balance.storageVersion" don't recognize chainB's type annotations, always use chainA's type annotations.

[jacogr]

Due to the way TS augmentation works (see an article by DigitalOcean, another HOWTO or the official documentation, it would either -

• apply the latest, i.e. latest in wins
• may complain when there are parameter mismatches

This is not something solvable on the API layer. Augmentations in TS are alway additive.

[cinlk]

well, Any idea to solve this problem? I think change TS declaration-merging rules is not a good way

[jacogr]

There is no "solution", as mentioned above, not any changes that can be made not "not do this" - this is just how TS types are augmented, it tries to apply all and there is one winner.

[jacogr]

Closing, works as expected with TS, non api-related.

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.