rust-library

To generate the file

fd -e go . ./golang_library | xargs -I {} sh -c 'echo "// {}"; cat "{}"' | tee library.go
fd -e ts . ./packages/legend-transac/src/ | xargs -I {} sh -c 'echo "// {}"; cat "{}"' | tee library.ts
fd -e rs . ./src/ | xargs -I {} sh -c 'echo "// {}"; cat "{}"' | tee library.rs

Finishing the app

Steps to publish the app

• cargo login ---> Se necesita una cuenta en crates.io, generar el token con permissos sufientes para publicar y actualizar versiones, luego verificar el email
• cargo package -p my-awesome-rabbitmq-lib
• cargo publish -p my-awesome-rabbitmq-lib

Pendientes:

• docs -> https://github.com/rust-lang/futures-rs/blob/7211cb7c5d8d859fa28ae55808c763a09d502827/.github/workflows/ci.yml#L306
• review Best Practices: https://www.cloudamqp.com/blog/part4-rabbitmq-13-common-errors.html

Features

It has std y eventsfeatures flags, std is the main app, events = ["serde", "strum", "strum_macros"] is used to handle types, payloads, enum, struct of the app

Test

Due to global vars like the connection and the publish-channel, the test can have different behaviors when are tested alone or with other tests. The global vars cannot be unset/reset, implies a mut static var, which is not allowed in Rust.