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
All notable changes to this project will be documented in this file.
4
+
5
+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
Contributions are **welcome** and will be fully **credited**.
4
+
5
+
Please read and understand the contribution guide before creating an issue or pull request.
6
+
7
+
## Etiquette
8
+
9
+
This project is open source, and as such, the maintainers give their free time to build and maintain the source code
10
+
held within. They make the code freely available in the hope that it will be of use to other developers. It would be
11
+
extremely unfair for them to suffer abuse or anger for their hard work.
12
+
13
+
Please be considerate towards maintainers when raising issues or presenting pull requests. Let's show the
14
+
world that developers are civilized and selfless people.
15
+
16
+
It's the duty of the maintainer to ensure that all submissions to the project are of sufficient
17
+
quality to benefit the project. Many developers have different skillsets, strengths, and weaknesses. Respect the maintainer's decision, and do not be upset or abusive if your submission is not used.
18
+
19
+
## Viability
20
+
21
+
When requesting or submitting new features, first consider whether it might be useful to others. Open
22
+
source projects are used by many developers, who may have entirely different needs to your own. Think about
23
+
whether or not your feature is likely to be used by other users of the project.
24
+
25
+
## Procedure
26
+
27
+
Before filing an issue:
28
+
29
+
- Attempt to replicate the problem, to ensure that it wasn't a coincidental incident.
30
+
- Check to make sure your feature suggestion isn't already present within the project.
31
+
- Check the pull requests tab to ensure that the bug doesn't have a fix in progress.
32
+
- Check the pull requests tab to ensure that the feature isn't already in progress.
33
+
34
+
Before submitting a pull request:
35
+
36
+
- Check the codebase to ensure that your feature doesn't already exist.
37
+
- Check the pull requests to ensure that another person hasn't already submitted the feature or fix.
38
+
39
+
## Requirements
40
+
41
+
If the project maintainer has any additional requirements, you will find them listed here.
42
+
43
+
### Coding Standards
44
+
45
+
We are using [`squizlabs/PHP_CodeSniffer`](https://github.com/squizlabs/PHP_CodeSniffer) to enforce coding standards in PHP files.
46
+
47
+
Run
48
+
49
+
```
50
+
$ composer codestyle
51
+
```
52
+
53
+
to automatically fix coding standard violations.
54
+
55
+
### Static Code Analysis
56
+
57
+
We are using [`phpstan/phpstan`](https://github.com/phpstan/phpstan) to statically analyze the code.
58
+
59
+
Run
60
+
61
+
```
62
+
$ composer phpstan
63
+
```
64
+
65
+
to run a static code analysis.
66
+
67
+
### Tests
68
+
69
+
We are using [`phpunit/phpunit`](https://github.com/sebastianbergmann/phpunit) to drive the development.
70
+
71
+
Run
72
+
73
+
```
74
+
$ composer test
75
+
```
76
+
77
+
to run all the tests.
78
+
79
+
Alternatively, you can run
80
+
81
+
```
82
+
$ composer test-fast
83
+
```
84
+
85
+
to get feedback quickly. This command will only run unit tests. Which should take around 100-200ms to run.
86
+
87
+
:exclamation: Make sure to run the whole test suite before opening a PR with the suggested changes.
88
+
89
+
### Mutation Tests
90
+
91
+
We are using [`infection/infection`](https://github.com/infection/infection) to ensure a minimum quality of the tests.
0 commit comments