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
refactor: rename aggregate::Saver method, move repositories into aggregate::repository mod (#249)
* refactor: rename aggregate::Saver::store in aggregate::Saver::save
* refactor: move aggregate::{Saver, Getter} to aggregate::repository::{Getter, Saver}
* feat: add .editorconfig
* chore: update CONTRIBUTING.md guidelines doc
* test(eventually-postgres): unmask errors with the integration test when conflict error is not detected
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+17-21Lines changed: 17 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
3
3
Thank you so much for considering contributing to `eventually`! :tada:
4
4
5
-
-[Contributing to `eventually`](#contributing-to-eventually)
6
-
-[What should I know before I get started?](#what-should-i-know-before-i-get-started)
7
-
-[I want to contribute, but I don't know what can I contribute to...](#i-want-to-contribute-but-i-dont-know-what-can-i-contribute-to)
8
-
-[Pull Requests](#pull-requests)
9
-
-[How should my Pull Request look like?](#how-should-my-pull-request-look-like)
10
-
-[Describe the scope of the PR](#describe-the-scope-of-the-pr)
11
-
-[Git commit messages](#git-commit-messages)
12
-
-[Rust styleguide](#rust-styleguide)
5
+
-[Contributing to `eventually`](#contributing-to-eventually)
6
+
-[What should I know before I get started?](#what-should-i-know-before-i-get-started)
7
+
-[I want to contribute, but I don't know what can I contribute to...](#i-want-to-contribute-but-i-dont-know-what-can-i-contribute-to)
8
+
-[Pull Requests](#pull-requests)
9
+
-[How should my Pull Request look like?](#how-should-my-pull-request-look-like)
10
+
-[Describe the scope of the PR](#describe-the-scope-of-the-pr)
11
+
-[Git commit messages](#git-commit-messages)
12
+
-[Rust styleguide](#rust-styleguide)
13
13
14
14
## What should I know before I get started?
15
15
@@ -18,27 +18,22 @@ where all the crates share the same dependencies and lock file.
18
18
(This might be changed in the future)
19
19
20
20
The workspace has the following crates:
21
-
-[`eventually`]\: the main crate, users should depend solely on this crate
22
-
-[`eventually-app-example`]\: an example application to showcase a (not-so) real-world example of how to use the library
23
21
24
-
Although `eventually-postgres` and `eventually-redis` are currently in the workspace, they might be moved outside the repository, into their own respective repository inside the organization. (For more info, check out #131 and #132)
22
+
-[`eventually`]\: the main crate, users should depend solely on this crate
23
+
-[`eventually-macros`]\: the crate that contains procedural macros to make the development experience nicer for users,
24
+
-[`eventually-postgres`]\: the crate that contains implementations of abstractions from `eventually` for PostgreSQL databases,
25
25
26
26
When submitting a PR involving one or more of these crates, please make sure to use the **corresponding label**.
27
27
28
28
### I want to contribute, but I don't know what can I contribute to...
29
29
30
30
If you want to contribute but you have no idea how, or what specific features are
31
-
missing, please check the [_What next?_ tracking issue](https://github.com/get-eventually/eventually-rs/issues/133).
31
+
missing, please check the [issues] page: we usually have some issues that are marked as "good for
32
+
beginners".
32
33
33
34
Being an open-source project, we are always looking for new contributors, so no matter
34
35
your level of Event Sourcing skills or language mastery, your PRs are always welcome :heart:
35
36
36
-
If you want to experiment and/or get familiar with the library, you can consider
37
-
trying to write a small application using the crate and send a message to our
38
-
[Gitter chat][gitter] to give visibility: we can add your example project to the
39
-
repository's `README` in order for other users to find it and draw inspiration
40
-
from your experience.
41
-
42
37
## Pull Requests
43
38
44
39
Before opening a Pull Request, check the [Issues section][issues] for an issue that might describe the feature you're considering adding.
@@ -48,11 +43,12 @@ implementation before the code review process. You can also reach out to our [Gi
48
43
features or other technical aspects of the crate.
49
44
50
45
In order to submit a PR, follow these steps:
46
+
51
47
1.**Fork** the repository
52
48
2.**Clone** your fork of the repository in your local machine
53
49
3. Add the upstream repository in your local machine copy:
0 commit comments