You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this issue you will get familiar with Rust's command line parser named Clap and you will operate with basic file IO. There is no need for understanding of Tackler-NG needed, but you will get familiar how its command line processing is working.
Introduction
It would be great to have tackler new and tackler init commands to create basic setup.
These would behave similarly as cargo new and cargo init, and do following steps:
Creates or initialize basic directory structure
Add default configuration files
Add an example transaction
Currently --config is mandatory argument, but this has to be changed so that there must be either --config, new or init.
Directory structure
The basic setup is following, and this should be created by new or init command:
The content of welcome.txn could be any valid Trackler transaction, for example these transactions
This must be implemented without any new dependencies (e.g. no new template crates). The content of all above files must be included into binary. That content of above files should be in each own Rust source code files, so that it's easy to update the content, and it's separated from actual code.
Testing
This functionality should be tested following way:
# create new setup
tackler new test
# verify tthe default configuration
tackler new --config test/journal/conf/tackler.toml
and "When specifying commands with command: Commands, they are required. Alternatively, you could do command: Option<Commands> to make it optional."
How to proceed
Thank you for thinking to contribute to Tackler-NG!
If you have any question, you could ask those here on this ticket or open new discussion (if you think it would take longer discussion). Read also Developer Documentation.
Happy hacking!
The text was updated successfully, but these errors were encountered:
Topics
With this issue you will get familiar with Rust's command line parser named Clap and you will operate with basic file IO. There is no need for understanding of Tackler-NG needed, but you will get familiar how its command line processing is working.
Introduction
It would be great to have
tackler new
andtackler init
commands to create basic setup.These would behave similarly as
cargo new
andcargo init
, and do following steps:Currently
--config
is mandatory argument, but this has to be changed so that there must be either--config
,new
orinit
.Directory structure
The basic setup is following, and this should be created by new or init command:
Correct content for configuration is located in files:
This must be implemented without any new dependencies (e.g. no new template crates). The content of all above files must be included into binary. That content of above files should be in each own Rust source code files, so that it's easy to update the content, and it's separated from actual code.
Testing
This functionality should be tested following way:
The integration tests are under tests/sh and test are run by test-runner-ng.sh
Pointers
command: Commands
, they are required. Alternatively, you could docommand: Option<Commands>
to make it optional."How to proceed
Thank you for thinking to contribute to Tackler-NG!
If you have any question, you could ask those here on this ticket or open new discussion (if you think it would take longer discussion). Read also Developer Documentation.
Happy hacking!
The text was updated successfully, but these errors were encountered: