• investigate existed tests
• investigate methods to test the output files
• write new tests

Utility wtest has failed test on Windows.
Fix the test, not realization.

Add negative tests for module type_constructor.
Module type_constructor https://github.com/Wandalen/wTools/tree/alpha/module/rust/type_constructor
Link on directory with tests for module type_constructor https://github.com/Wandalen/wTools/tree/alpha/rust/test/dt/type_constructor
Write tests for implementation of single, homopair, pair and many.

Negative testing :

• test that throws compile time errors
• test that throws runtime errors

For example, the mismatched types error is the compile time error.

Use trybuild to test compile time errors.
Example of such test

Fix test of utility publisher

Test run with fail

Required :

• Windows

Implement routine glob_is in utility wpublisher :

• create new module path in https://github.com/Wandalen/wTools/tree/alpha/rust/impl/publisher/tools
• implement and cover the method
• use method in https://github.com/Wandalen/wTools/blob/alpha/rust/impl/publisher/commands/publish.rs#L47
• cover new behavior

Willbe Task
Implement a function that takes iterator of Workspaces and OrderStrategy as arguments and returns an iterator over Crates:

workspaces_crates_iterate( workspace : impl Iterator<&Workspace>, order : OrderStrategy ) -> impl Iterator<Item = &Crate>;

Willbe Task
Implement a function that takes Workspace and OrderStrategy as arguments and returns an iterator over Crates:

workspace_crates_iterate( workspace : Workspace, order : OrderStrategy ) -> impl Iterator<Item = &Crate>;

Probably this is solution for issue

Willbe Task
// to do

Willbe Task
// to do

Willbe Task
Implement the function :
cretes_publish( crates: Vec, how : BumpType, options: PublishOptions ) -> Result<()>;

Willbe Task
Implement the function :
crate_publish_verify( crate : Crate, how : BumpType ) -> Result<()>;

Module wtools aggregates many modules in directory) rust.
Each module is included in wtools with the feature.

The tests of module wtools fails if the feature timer enabled.

• investigate features and tests of modules wtools and time_tools
• find a solution to fix the issue
• implement the solution

An example of what it might look like is notan.
The state can be the WCA itself or another type with certain restrictions.
It can be used to execute a chain of commands, where "subject" is a command from the map of commands in command aggregator.

Example of initialization:

let ca = wca::commands_aggregator()
  .changing_exit_code( true )
  .commands( commands::commands_form() )
  .form();

ca.set_context(&ca); // or map of commands, or function to setup context(think about it)
ca.instruction_perform( args.join( " " ).as_str() )

Usage example:

pub fn command_name( instruction : &crate::instruction::Instruction, ctx : &mut State ) -> Result< (), BasicError >
{
  // do something
}

Description:

In the workflow table within the file Readme.md, the colon symbols are missing in the links, leading to incorrect display and execution of the workflow.

Steps to Reproduce:

1. Navigate to the file Readme.md.
2. Locate the workflow table.
3. Check the links in the table and observe the absence of colon symbols (":").

Expected Result:

Colon symbols should be present in the links to ensure proper display and execution of the workflow.

Actual Result:

Colon symbols are missing in the links of the workflow table.

Suggested Fix:

Add the missing colon symbols in the links of the workflow table to address the issue.

Willbe task.
Implement a function which will validate links in the crate.

check_links( crate: Crate ) -> Result<()>;

Willbe Task
// to do

// qqq : check and improve quality of generated documentation
// qqq : make sure that documentation for each entity is up to date
// qqq : document, explain why and add example of generated code. if possible to improve -- suggest improvements
// qqq : test that and document example of generated code

General doc review + macro simplification

Willbe Task
// to do

Willbe Task
// to do

Extend documentation of module wca.
The base documentation is added in #953

As a user, I want to get my Enum-s from the arguments
E.g.:

enum HelpFormat {
  MarkDown,
  Json,
  /* ... */
}

let help_format: HelpFormat = args.get_owned().unwrap();

Help information:

Args::get_owned: [ location ]
Props::get_owned: [ location ]

get_owned returns a value that can be derived from Value, so if you extend Type and Value, you can pass them Enums
Type and Value: [ location ]

Willbe task.
Implement a function that takes Puthbuff and OrderStrategy as arguments and returns an iterator over Crates.

crates_iterate( path : PathBuff, order : OrderStrategy ) -> impl Iterator<Item = &Crate>;

1. most of the documentation refers to "the Former trait". there is no trait named Former, only a derive macro.
2. the primary purpose of the builder pattern is the ability to enforce invariant when the structure is built, and to not expose the internal structure (eg. so that you could switch from a HashMap to a DashMap in semver-compatible versions). it is not clear how you would achieve either of these.

Willbe Task
// to do

• extend enum ColorType of module _video_experiment by type YUV
• implement handling of the type for each encoder
• test new color type, write test for each encoder