re
/
viper
forked from mirror/viper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: propose dropping file writing support 

Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>
This commit is contained in:
Mark Sagi-Kazar 2021-09-22 23:10:51 +02:00
parent a0f1caa4ed
commit c943b3ef27
No known key found for this signature in database
GPG Key ID: 31AB0439F4C5C90E
2 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/adr/0002-prefer-making-backward-compatible-changes.md
View File

@ -10,6 +10,8 @@ Referenced by [3. Extract components with heavy dependencies from the core](0003
Referenced by [4. Use separate GitHub organization for new packages](0004-use-separate-github-organization-for-new-packages.md) Referenced by [4. Use separate GitHub organization for new packages](0004-use-separate-github-organization-for-new-packages.md)
Referenced by [7. Drop writing support](0007-drop-writing-support.md)
## Context ## Context
Architecturally speaking Viper became a giant over the years: it hides a lot of complexity behind a simple interface. Architecturally speaking Viper became a giant over the years: it hides a lot of complexity behind a simple interface.

22
docs/adr/0007-drop-writing-support.md Normal file
View File

@ -0,0 +1,22 @@
# 7. Drop writing support
Date: 2021-09-22
## Status
Proposed
References [2. Prefer making backward compatible changes](0002-prefer-making-backward-compatible-changes.md)
## Context
The number one source of issues for Viper comes from the fact that it supports both reading and writing.
It causes concurrency issues and has lots of inconsistencies.
## Decision
Drop file writing support from Viper in v2.
## Consequences
This is going to be a major breaking change in the library, but it will make maintenance significantly easier.