processor/Cargo.toml

[package]
name = "processor"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
csv = "1.1"
fpdec = "0.5"
serde = { version = "1.0", features = ["derive"] }
serde_with = "2.0"
cargo: init build system 2022-08-22 17:08:51 +02:00			`[package]`
			`name = "processor"`
			`version = "0.1.0"`
			`edition = "2021"`

			`# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html`

			`[dependencies]`
transaction: add CSV deserialization It is unfortunate that both [1] and [2] conspire to make this code way worse than it could otherwise be with a saner (de)serialization format. We both need to introduce `TransactionRecord` due to tagged enums not being powerful enough in CSV, and make its `amount` field optional to deal with the varying number of fields for each kind of transaction. [1]: https://github.com/BurntSushi/rust-csv/issues/211 [2]: https://github.com/BurntSushi/rust-csv/issues/172 2022-08-23 11:24:34 +02:00			`csv = "1.1"`
cargo: add 'fpdec' dependency Instead of implementing custom fixed-point decimal numbers, let's make use of an existing implementation until it is deemed inappropriate. 2022-08-22 17:25:16 +02:00			`fpdec = "0.5"`
transaction: add CSV deserialization It is unfortunate that both [1] and [2] conspire to make this code way worse than it could otherwise be with a saner (de)serialization format. We both need to introduce `TransactionRecord` due to tagged enums not being powerful enough in CSV, and make its `amount` field optional to deal with the varying number of fields for each kind of transaction. [1]: https://github.com/BurntSushi/rust-csv/issues/211 [2]: https://github.com/BurntSushi/rust-csv/issues/172 2022-08-23 11:24:34 +02:00			`serde = { version = "1.0", features = ["derive"] }`
			`serde_with = "2.0"`