Purpose of the Proposal
We request funding for the further development of the <a href="https://www.npmjs.com/package/polkadot-typed-api" target="_blank" rel="noopener">polkadot-typed-api</a> library, which provides a typed access to the Polkadot API. Our goal is to enhance the ecosystem by making development more convenient and safe through precise typing.
Project Description
The <a href="https://www.npmjs.com/package/polkadot-typed-api" target="_blank" rel="noopener">polkadot-typed-api </a>library does not introduce new methods but wraps existing API calls in convenient functions that return typed data. This allows developers to use the Polkadot API with explicit type declarations, significantly reducing the likelihood of errors and simplifying the development process.
Current Results
Currently, the library covers about 5% of all available methods, with an emphasis on 20% of query calls. We plan to significantly increase this coverage, aiming to reach 50% for query calls by the end of 2024 and 100% by the end of 2025.
Challenges and Issues
One of the main challenges is the detailed study of tx calls, each of which requires considerable time investment. We are actively working on this task; however, it demands additional resources and time for comprehensive analysis.
UPDATE:
In the course of discussions with the community, we have chosen a new direction for our development: instead of manually defining types, we will implement dynamic type generation. This approach will be included in the second version of the library.
Dynamic type generation is crucial as it allows for real-time adaptation to changes in the Polkadot API, ensuring that the library remains current with the latest updates and enhancements. This will not only streamline our development process but also provide developers with a more robust and flexible toolset, reducing the likelihood of errors associated with manual typing.
As a result of this strategic shift, we have updated our timelines. We now plan to complete work on reading methods, achieving 100% coverage by the end of 2024, which will be included in version 2.0. Following that, we will focus on transaction methods, with completion targeted for Q1 2025.
Impact on the Developer Community
The development of the <a href="https://www.npmjs.com/package/polkadot-typed-api" target="_blank" rel="noopener">polkadot-typed-api</a> library will have a significant impact on the developer community within the Polkadot ecosystem:
<ul>
<li>Simplification of API Interaction. Typed access to the API frees developers from manually checking and processing data types, enabling faster integration of functions.</li>
<li>Increased Code Security. Explicit typing reduces the risk of errors associated with incorrect data types, which is especially important in blockchain development, where mistakes can lead to financial losses.</li>
<li>Accelerated Development. The library will provide convenient wrappers for existing method calls, allowing developers to focus on business logic and functionality.</li>
<li>Access to Documented Methods. We plan to document every method of each pallet, creating a user-friendly resource for developers.</li>
<li>Expansion of the Developer Community. Easier access to typed data will attract more developers to the Polkadot ecosystem, contributing to the development and resilience of the ecosystem.</li>
<li>Support for New Developers. The library will serve as an excellent resource for newcomers, making the learning process more intuitive and less confusing.</li>
<li>Incentive for Collaboration. The <a title="GitHub" href="https://github.com/dmitrytarassov/crypto-tools/tree/main/packages/polkadot-typed-api" target="_blank" rel="noopener">openness of the code </a>and community support for the library can foster collaboration among developers.</li>
</ul>
Conclusion
We are not requesting significant funds, but it is crucial for us to understand that the community values our work. The development of the polkadot-typed-api library will be an important step towards improving the Polkadot ecosystem by supporting developers and enhancing code quality, ultimately contributing to the growth of the community.

Purpose of the Proposal
We request funding for the further development of the <a href="https://www.npmjs.com/package/polkadot-typed-api" target="_blank" rel="noopener">polkadot-typed-api</a> library, which provides a typed access to the Polkadot API. Our goal is to enhance the ecosystem by making development more convenient and safe through precise typing.
Project Description
The <a href="https://www.npmjs.com/package/polkadot-typed-api" target="_blank" rel="noopener">polkadot-typed-api </a>library does not introduce new methods but wraps existing API calls in convenient functions that return typed data. This allows developers to use the Polkadot API with explicit type declarations, significantly reducing the likelihood of errors and simplifying the development process.
Current Results
Currently, the library covers about 5% of all available methods, with an emphasis on 20% of query calls. We plan to significantly increase this coverage, aiming to reach 50% for query calls by the end of 2024 and 100% by the end of 2025.
Challenges and Issues
One of the main challenges is the detailed study of tx calls, each of which requires considerable time investment. We are actively working on this task; however, it demands additional resources and time for comprehensive analysis.
Impact on the Developer Community
The development of the <a href="https://www.npmjs.com/package/polkadot-typed-api" target="_blank" rel="noopener">polkadot-typed-api</a> library will have a significant impact on the developer community within the Polkadot ecosystem:
<ul>
<li>Simplification of API Interaction. Typed access to the API frees developers from manually checking and processing data types, enabling faster integration of functions.</li>
<li>Increased Code Security. Explicit typing reduces the risk of errors associated with incorrect data types, which is especially important in blockchain development, where mistakes can lead to financial losses.</li>
<li>Accelerated Development. The library will provide convenient wrappers for existing method calls, allowing developers to focus on business logic and functionality.</li>
<li>Access to Documented Methods. We plan to document every method of each pallet, creating a user-friendly resource for developers.</li>
<li>Expansion of the Developer Community. Easier access to typed data will attract more developers to the Polkadot ecosystem, contributing to the development and resilience of the ecosystem.</li>
<li>Support for New Developers. The library will serve as an excellent resource for newcomers, making the learning process more intuitive and less confusing.</li>
<li>Incentive for Collaboration. The <a title="GitHub" href="https://github.com/dmitrytarassov/crypto-tools/tree/main/packages/polkadot-typed-api" target="_blank" rel="noopener">openness of the code </a>and community support for the library can foster collaboration among developers.</li>
</ul>
Conclusion
We are not requesting significant funds, but it is crucial for us to understand that the community values our work. The development of the polkadot-typed-api library will be an important step towards improving the Polkadot ecosystem by supporting developers and enhancing code quality, ultimately contributing to the growth of the community.

Proposal for Funding the Development of the polkadot-typed-api Library

Treasury

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least `amount`.

### Details
NOTE: For record-keeping purposes, the proposer is deemed to be equivalent to the
beneficiary.

### Parameters
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The destination account for the transfer.

## Events

Emits [`Event::SpendApproved`] if successful.

- **Problem Statement:** Requesting funding for enhancing the polkadot-typed-api library to provide typed access to the Polkadot API, aiming to simplify development and increase safety.
- **Significance:** Improving the library will streamline development, reduce errors, and attract more developers to the Polkadot ecosystem.
- **Proposed Solution:** Implement dynamic type generation to adapt to changes in the Polkadot API, aiming for 100% coverage by 2024 for reading methods and by Q1 2025 for transaction methods.
- **Expected Outcomes:** Simplified API interaction, increased code security, accelerated development, expanded developer community, support for new developers, and incentive for collaboration.

#1196 Proposal for Funding the Development of the polkadot-typed-api Library

No Active Proposals