Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Events Handling (#1) #2

Merged
merged 42 commits into from
Aug 30, 2021
Merged
Show file tree
Hide file tree
Changes from 13 commits
Commits
Show all changes
42 commits
Select commit Hold shift + click to select a range
6697475
Basic project structure with Event and VersionedEvent impls
ilslv Aug 13, 2021
a6e1847
Add Makefile, GitHub Actions, PR and Issue templates
ilslv Aug 13, 2021
238058d
Add EventInitialized, EventSourced and InitialEvent
ilslv Aug 13, 2021
83f9911
Fix CI
ilslv Aug 13, 2021
f31ca0c
Finally check uniqueness of event_type() and ver() at compile-time!
ilslv Aug 16, 2021
42c5b4d
Add docs explaining unique checks macro shenanigans [skip ci]
ilslv Aug 16, 2021
7dfe985
Add ability to skip uniqueness check for event_type and ver for Event…
ilslv Aug 17, 2021
7df18ef
Add more tests
ilslv Aug 17, 2021
d454eaf
Final touches
ilslv Aug 17, 2021
c61e8bb
Use nightly toolchain on CI
ilslv Aug 17, 2021
32aec5d
Fix CI
ilslv Aug 17, 2021
aa8f2b4
Remove stable and beta toolchains in testing
ilslv Aug 17, 2021
e815e60
CHANGELOG
ilslv Aug 17, 2021
11107d1
Merge branch 'master' into 1-event-sourcing
tyranron Aug 17, 2021
b048ca1
Introduce EventName and EventVersion and support them in proc-macros
ilslv Aug 17, 2021
c6f1ff9
CHANGELOG
ilslv Aug 17, 2021
d7647b6
Merge branch 'master' into 1-event-sourcing
ilslv Aug 17, 2021
c477378
Some corrections [skip ci]
tyranron Aug 17, 2021
5166708
Merge remote-tracking branch 'origin/1-event-sourcing' into 1-event-s…
tyranron Aug 17, 2021
4bd1c85
Replace event_type() with name() everywhere [skip ci]
ilslv Aug 17, 2021
8bc5e8c
Add es feature-gates [skip ci]
ilslv Aug 17, 2021
418b233
Split derive and es feature-gates [skip ci]
ilslv Aug 17, 2021
683456b
Use arcana-core crate for arcana-codegen-impl docs [skip ci]
ilslv Aug 17, 2021
7a8ceb5
WIP [skip ci]
ilslv Aug 17, 2021
8a9b4ec
Cover Event derive macro with docs [skip ci]
ilslv Aug 17, 2021
32f233f
Cover VersionedEvent derive macro with docs [skip ci]
ilslv Aug 17, 2021
18a0c1a
Move events uniqueness check to arcana_codegen crate [skip ci]
ilslv Aug 18, 2021
de5edea
Use only required number of events in uniqueness check [skip ci]
ilslv Aug 20, 2021
fb0260a
Add arcana-codegen-shim [skip ci]
ilslv Aug 20, 2021
d74ae8e
Add MSRV check
ilslv Aug 23, 2021
eff3a0a
Fix CI
ilslv Aug 23, 2021
373d0c1
Remove safety_guard dependency
ilslv Aug 23, 2021
4ad217b
Some corrections [skip ci]
tyranron Aug 24, 2021
088db1a
Corrections
ilslv Aug 25, 2021
8cea01b
Correction
ilslv Aug 25, 2021
0a40645
Disable -Z minimal-versions for now on CI MSRV check
ilslv Aug 25, 2021
8a84f85
Some corrections [skip ci]
tyranron Aug 25, 2021
23306f4
Merge remote-tracking branch 'origin/1-event-sourcing' into 1-event-s…
tyranron Aug 25, 2021
2d2c92d
Try to support generics in internal uniqueness glue code
ilslv Aug 26, 2021
843cae5
Hide docs dependencies behind the feature
ilslv Aug 26, 2021
7685c03
Corrections
ilslv Aug 26, 2021
f522fcf
Corrections
tyranron Aug 30, 2021
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 56 additions & 0 deletions .github/ISSUE_TEMPLATE/Bug.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
name: Bug
about: Report a bug related to the project.
labels: bug
---

Revealed from <paste issue/PR reference>
<and/or>
Caused by <paste issues/PRs references>
<and/or>
Related to <paste issues/PRs references>

<Remove the lines above if there are no related issues/PRs>




## Summary

<Summarize the bug encountered concisely>




## Steps to reproduce

<How one can reproduce the issue - this is very important>




## What is the current _bug_ behavior?

<What actually happens>




## What is the expected _correct_ behavior?

<What you should see instead>




## Relevant logs and/or screenshots

<Paste any relevant logs - please use code blocks (`````) to format console output, logs, and code as it's very hard to read otherwise>
<If there is no logs/screenshots - just remove this section completely>



## Possible fixes

<If you can, link to the line of code that might be responsible for the problem>
<If there is nothing to propose - just remove this section completely>
48 changes: 48 additions & 0 deletions .github/ISSUE_TEMPLATE/Feature proposal.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
---
name: Feature proposal
about: Suggest a new feature for the project.
labels: feature
---

Revealed from <paste issues/PRs references>
<and/or>
Related to <paste issues/PRs references>

<Remove the lines above if there are no related issues/PRs>




## Problem to solve

<Describe the problem that feature is going to solve>




## Proposal

<Give a detailed proposal of problem solving, describe its pros and cons>




## Prior art

<Provide a link and brief info about attempts and proposals which tried to solve this problem before, or are quite relative to this proposal>
<If there is nothing to refer - just remove this section completely>




## Alternatives

<Provide a brief description of alternative solutions, describe their pros and cons>




## Links & references

<Provide links and references that are related to this proposal and problem>
<If there is nothing to refer - just remove this section completely>
23 changes: 23 additions & 0 deletions .github/ISSUE_TEMPLATE/Question.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
name: Question
about: Ask a question related to the project.
labels: question
---

Related to <paste issues/PRs references>

<Remove the lines above if there are no related issues/PRs>




## Background

<Describe the preconditions and the situation which lead to your question>




## Question

<Ask the concrete question (or multiple questions)>
25 changes: 25 additions & 0 deletions .github/ISSUE_TEMPLATE/Roadmap.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
name: Roadmap
about: Provide a roadmap for reaching a milestone or implementing a big feature.
labels: roadmap
---

Related to <paste issues/PRs references>

<Remove the lines above if there are no related issues/PRs>




## Summary

<Summarize the meaning and the purpose of this roadmap>




## Roadmap

<Describe the roadmap as a numbered task list, where each step should contain references to its issue/PR and checked after its completion>

- [ ] 1. First step. (<paste issue/PR references>)
38 changes: 38 additions & 0 deletions .github/ISSUE_TEMPLATE/Task.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
---
name: Task
about: Describe a task to be done.
---

Part of <paste issue/PR reference>
<and/or>
Revealed from <paste issue/PR reference>
<and/or>
Required for <paste issues/PRs references>
<and/or>
Requires <paste issues/PRs references>
<and/or>
Related to <paste issues/PRs references>

<Remove the lines above if there are no related issues/PRs>




## Background

<Describe the preconditions and the situation which lead to the problem>




## Problem to solve

<Describe the problem to be solved by this task>




## Possible solutions

<Describe possible solutions and assumptions about them>
<If there is nothing to propose - just remove this section completely>
70 changes: 70 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
---
name: Task
about: Perform a task related to the project.
---

<To use "Bugfix" PR template add `&template=Bugfix.md` to this page's URL>

<To use "Roadmap" PR template add `&template=Roadmap.md` to this page's URL>

<To use "Release" PR template add `&template=Release.md` to this page's URL>

<Remove everything above before submitting this PR>


Resolves <paste issue reference>
<and/or>
Part of <paste issue/PR reference>
<and/or>
Required for <paste issues/PRs references>
<and/or>
Requires <paste issues/PRs references>
<and/or>
Related to <paste issues/PRs references>

<Remove the lines above if there are no related issues/PRs>




## Synopsis

<Give a brief overview of the problem>




## Solution

<Describe how exactly the problem is (or will be) resolved>




## Checklist

- Created PR:
- [ ] In [draft mode][l:1]
- [ ] Name contains `Draft: ` prefix
- [ ] Name contains issue reference
- [ ] Has `k::` labels applied
- [ ] Has assignee
- [ ] Documentation is updated (if required)
- [ ] Tests are updated (if required)
- [ ] Changes conform code style
- [ ] CHANGELOG entry is added (if required)
- [ ] FCM (final commit message) is posted
- [ ] and approved
- [ ] [Review][l:2] is completed and changes are approved
- Before merge:
- [ ] Milestone is set
- [ ] PR's name and description are correct and up-to-date
- [ ] `Draft: ` prefix is removed
- [ ] All temporary labels are removed





[l:1]: https://help.github.com/en/articles/about-pull-requests#draft-pull-requests
[l:2]: https://help.github.com/en/articles/reviewing-changes-in-pull-requests
55 changes: 55 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/Bugfix.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
---
name: Bugfix
about: Resolve a bug related to the project.
labels: enhancement
---

<Remove everything above before submitting this PR>


Resolves <paste issue reference>




## Synopsis

<Give a brief overview of the problem>




## Solution

<Describe how exactly the problem is (or will be) resolved>




## Checklist

- Created PR:
- [ ] In [draft mode][l:1]
- [ ] Name contains `Draft: ` prefix
- [ ] Name contains issue reference
- [ ] Has `k::` labels applied
- [ ] Has assignee
- [ ] Documentation is updated (if required)
- [ ] Tests are updated (if required)
- [ ] Changes conform code style
- [ ] CHANGELOG entry is added (if required)
- [ ] FCM (final commit message) is posted
- [ ] and approved
- [ ] [Review][l:2] is completed and changes are approved
- Before merge:
- [ ] Milestone is set
- [ ] PR's name and description are correct and up-to-date
- [ ] `Draft: ` prefix is removed
- [ ] All temporary labels are removed





[l:1]: https://help.github.com/en/articles/about-pull-requests#draft-pull-requests
[l:2]: https://help.github.com/en/articles/reviewing-changes-in-pull-requests
41 changes: 41 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE/Release.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
---
name: Release
about: Prepare a new release of the project.
labels: enhancement, k::documentation
---

<Remove everything above before submitting this PR>


Prepares [<paste release version>](<paste milestone link>) release.




## Checklist

- Created PR:
- [ ] In [draft mode][l:1]
- [ ] Name contains `Draft: ` prefix
- [ ] Name contains issue reference
- [ ] Has `k::` labels applied
- [ ] Has assignee
- [ ] Documentation is updated (if required)
- [ ] Tests are updated (if required)
- [ ] Changes conform code style
- [ ] CHANGELOG entry is added (if required)
- [ ] FCM (final commit message) is posted
- [ ] and approved
- [ ] [Review][l:2] is completed and changes are approved
- Before merge:
- [ ] Milestone is set
- [ ] PR's name and description are correct and up-to-date
- [ ] `Draft: ` prefix is removed
- [ ] All temporary labels are removed





[l:1]: https://help.github.com/en/articles/about-pull-requests#draft-pull-requests
[l:2]: https://help.github.com/en/articles/reviewing-changes-in-pull-requests
Loading