lemmy/crates/db_views/Cargo.toml

[package]
name = "lemmy_db_views"
version = "0.1.0"
edition = "2018"

[lib]
doctest = false

[dependencies]
lemmy_db_queries = { path = "../db_queries" }
lemmy_db_schema = { path = "../db_schema" }
diesel = { version = "1.4.5", features = ["postgres","chrono","r2d2","serde_json"] }
serde = { version = "1.0.123", features = ["derive"] }
log = "0.4.14"
url = "2.2.0"

[dev-dependencies]
serial_test = "0.5.1"
Split lemmy_db into lemmy_db_queries, lemmy_db_aggregates and lemmy_db_views 2020-12-21 16:30:34 +00:00			`[package]`
			`name = "lemmy_db_views"`
			`version = "0.1.0"`
			`edition = "2018"`

Support plain `cargo test` and disable unused doctests for speed Since DB tests execute diesel migrations automatically, concurrent execution causes flaky failures from simultaneous migrations. This can be worked around using `cargo test --workspace -- --test-threads=1`, which is what the CI config does, but this is not intuitive for newcomer developers and unnecessarily slows down the test suite for the majority of tests which are safe to run concurrently. This fixes this issue by integrating with the small test crate `serial_test` and using it to explicitly mark DB tests to run sequentially while allowing all other tests to run in parallel. Additionally, this greatly improves the speed of `cargo test` by disabling doc-tests in all crates, since these are aren't currently used and cargo's doc-test pass, even when no doc-tests exist, has significant overhead. On my machine, this change significantly improves test suite times by about 85%, making it much more practical to develop with tools like `cargo watch` auto-running tests. 2021-02-25 19:43:39 +00:00			`[lib]`
			`doctest = false`

Split lemmy_db into lemmy_db_queries, lemmy_db_aggregates and lemmy_db_views 2020-12-21 16:30:34 +00:00			`[dependencies]`
Move most code into crates/ subfolder 2021-01-20 15:21:27 +00:00			`lemmy_db_queries = { path = "../db_queries" }`
			`lemmy_db_schema = { path = "../db_schema" }`
Split lemmy_db into lemmy_db_queries, lemmy_db_aggregates and lemmy_db_views 2020-12-21 16:30:34 +00:00			`diesel = { version = "1.4.5", features = ["postgres","chrono","r2d2","serde_json"] }`
Trying to upgrade lemmys deps. 2021-02-01 20:56:37 +00:00			`serde = { version = "1.0.123", features = ["derive"] }`
			`log = "0.4.14"`
Store activitypub endpoints in database (#162) Address review comments Store Activitypub urls in database (fixes #808) Co-authored-by: Felix Ableitner <me@nutomic.com> Reviewed-on: https://yerbamate.ml/LemmyNet/lemmy/pulls/162 Co-Authored-By: nutomic <nutomic@noreply.yerbamate.ml> Co-Committed-By: nutomic <nutomic@noreply.yerbamate.ml> 2021-02-04 16:34:58 +00:00			`url = "2.2.0"`
Support plain `cargo test` and disable unused doctests for speed Since DB tests execute diesel migrations automatically, concurrent execution causes flaky failures from simultaneous migrations. This can be worked around using `cargo test --workspace -- --test-threads=1`, which is what the CI config does, but this is not intuitive for newcomer developers and unnecessarily slows down the test suite for the majority of tests which are safe to run concurrently. This fixes this issue by integrating with the small test crate `serial_test` and using it to explicitly mark DB tests to run sequentially while allowing all other tests to run in parallel. Additionally, this greatly improves the speed of `cargo test` by disabling doc-tests in all crates, since these are aren't currently used and cargo's doc-test pass, even when no doc-tests exist, has significant overhead. On my machine, this change significantly improves test suite times by about 85%, making it much more practical to develop with tools like `cargo watch` auto-running tests. 2021-02-25 19:43:39 +00:00
			`[dev-dependencies]`
			`serial_test = "0.5.1"`