Comments (3)
I'm having second thoughts on this. I think that what I'm suggesting in here is wrong. The whole point of having a Codec
type is that the output of the decoder is the same type as the input of the encoder... If that's not the case, then it's just something else, but not a Codec
.
That being said, we could solve this in our end by using enhanced encoders wherever necessary... 🤔
from polkadot-api.
The more I think about this, the more I realize that we should make this breaking change ASAP. I keep finding more and more cases where the encoder and the decoder should have different types... We should tackle this before it's too late, the longer we wait the more difficult it's going to be to make this change in the future.
from polkadot-api.
Ok, so after spiking this task and I ended up realizing that this is a really bad idea.
The output of the decoder should always match with the input of the encoder.
That being said, I have come up with a very nice solution to the problem that I described above. However, I will be explaining that solution in a separate issue.
from polkadot-api.
Related Issues (20)
- Round-robin over several WS endpoints
- @polkadot-api/utils should be dependency not dev dependency of @polkadot-api/substrate-client HOT 4
- Granular compatibility check HOT 1
- Whitelist TS suggestion for pallet wildcard is not working
- Document rpc node requirements HOT 15
- Typings problem on v0.11 HOT 2
- Values typed as `FixedSizeBinary` is only an instance of `Binary`
- Add `Polkadot People Chain` as a known chain HOT 8
- Generated API docs based on metadata HOT 13
- Improve descriptors package DX
- `file:` protocol break `yarn install --immutable` HOT 3
- Missing/incompatible ESM typings for `polkadot-api/polkadot-sdk-compat` HOT 1
- Internal RPC error when trying to use Polkadot-People chain with light client HOT 3
- Intermittent infinite loop when initiating multiple chains at the same time HOT 5
- support Encointer as known-chain HOT 1
- Cannot read properties of undefined (reading 'number') HOT 2
- Query results in indefinitely pending promise when encountering JSON-RPC error HOT 4
- InvalidTxError: { "type": "Invalid", "value": { "type": "Stale" } } HOT 3
- Uknown operationId HOT 3
- unioned descriptors doesn't compile in batch call HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from polkadot-api.