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
Copy file name to clipboardExpand all lines: README.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,10 @@ This is a great process for bug fixes, simple features and purely additive chang
12
12
13
13
However, if you are making a significant change to the way Vortex functions, you may need to write an RFC first. Some example changes that would require an RFC:
14
14
15
-
* Making a risky change to the format, such as adding new required fields to file metadata
16
-
* Rearchitecting core components of Vortex, or wide-ranging refactors that might break language bindings
17
-
* Creating new libraries or SDKs that we expect others to adopt
18
-
* Making changes to subsystems that are likely to affect performance if not done thoughfully, such as the core IO traits
15
+
- Making a risky change to the format, such as adding new required fields to file metadata
16
+
- Rearchitecting core components of Vortex, or wide-ranging refactors that might break language bindings
17
+
- Creating new libraries or SDKs that we expect others to adopt
18
+
- Making changes to subsystems that are likely to affect performance if not done thoughfully, such as the core IO traits
19
19
20
20
## Process
21
21
@@ -70,3 +70,14 @@ Remove the build output:
70
70
```sh
71
71
bun run clean
72
72
```
73
+
74
+
### Formatting
75
+
76
+
We use [`prettiest`](https://prettier.io/) to format the code and documents, and check it in CI.
0 commit comments