-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Book] Examples #32
Comments
Can I work on this |
Hi @raizo07! |
hello @dmirgaleev i am a blockchain developer and a technical writer here are some of the docs i have writting: please assign me :) |
Hi @martinvibes! |
hello @dmirgaleev i am a technical writer please can i work on this issue :) and would love to be a contributor here are some of the docs i have writting: |
Hi @martinvibes! |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI am a web3 frontend developer and Technical writer skilled in Typescript, Javascript, Solidity, Cairo and Rust. I also do lots off documentations on Readme files. This will help me in carrying out this task seamlessly. I have contributed to open source projects like Stark Quest How I plan on tackling this issue
|
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedCan I be assigned this How I plan on tackling this issueI can do this |
I am applying to this issue via OnlyDust platform. My background and how it can be leveraged@dmirgaleev can I work on this please |
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedI’m Benjamin, and I’m excited to work on adding a new documentation page for our project that will list reference test files. Since joining OnlyDust, I’ve made 18 contributions, and I’m confident in my documentation skills, so I believe I can make this page very useful for our community. How I plan on tackling this issueThe goal is to set up a page that lists various test files.
I’ll save this new markdown file in the docs/pages/examples.md path to keep everything organized. To help me gather all the info and examples,
|
I am applying to this issue via OnlyDust platform. My background and how it can be leveragedMy name is Collins Ikechukwu. I'm a full stack blockchain developer developer.amd a technical writer How I plan on tackling this issue
|
@dmirgaleev Thanks will begin working asap |
Hello @Benjtalkshow! Welcome aboard! Please don't hesitate to join our Telegram group https://t.me/baking_bad_odhack to ask questions and share your progress! Happy hacking! |
Alright. Thanks |
Friendly heads up that you have until Sunday (October 6) to push your final PR. @Benjtalkshow |
Alright ser |
Can I be assigned this issue @dmirgaleev |
Hi @dmirgaleev please can I be assigned to this issue.. I am available to work |
Hello @dmirgaleev, may I give this a try? |
hello @dmirgaleev can i work on this issue ? |
@dmirgaleev I'd love to contribute here. I understand the structure of test data and happy to document it. I can also improve on example programs (to have arguments for example) |
@baitcode awesome, let's go!:) |
Can't start today. Will start working on Friday! |
No worries, no strict timelines for this |
Hey @baitcode! What's the status? |
@dmirgaleev I've postponed it a bit, as you mentioned that timelines are not strict. Been doing cairo quests on NodeGuardian to get more acquainted with the language. I'll submit PR soon. Pardon for silence. https://nodeguardians.io/character/baitcode |
- Added comments to test basic test program - Created a cript to generate documentation based on comments + test_files folder structure - A bit of cleanup in test data generation scripts + support for arguments This resolves issue dipdup-io#32
@dmirgaleev created draft PR for this issue. I think I'll finish today or the next day. |
@dmirgaleev Could you, please, review? that is how result looks like |
* - Added custom arguments to basic - Added comments to test basic test program - Created a cript to generate documentation based on comments + test_files folder structure - A bit of cleanup in test data generation scripts + support for arguments This resolves issue #32
Resolved in #85 |
Add a documentation page containing a list of reference test files, namely:
It also has to contain a brief description of what the program does, its arguments (if applicable).
Path to your markdown file:
docs/pages/examples.md
References:
The text was updated successfully, but these errors were encountered: