mirror of
https://github.com/Xahau/xahaud.git
synced 2025-12-01 16:05:52 +00:00
Add instructions for resolving validation failures:
* Add instructions to the workflow at the point where the failure would occur, which is where someone experiencing a failure is most likely to look. To keep things simple, the instructions are always printed. The assumption is that if the job succeeds, nobody is likely to look anyway. * Provides the diff of the failure as an artifact, so the user can apply it directly to their repo. * Also update the levelization/README.md to clarify the levels a little bit.
This commit is contained in:
committed by
Nik Bougalis
parent
3b33318dc8
commit
b2bf2b6e6b
@@ -16,10 +16,14 @@ reflect these rules. Whenever possible, developers should refactor any
|
||||
levelization violations they find (by moving files or individual
|
||||
classes). At the very least, don't make things worse.
|
||||
|
||||
The table below summarizes the _desired_ division of modules. The levels
|
||||
are numbered from the bottom up with the lower level, lower numbered,
|
||||
more independent modules listed first, and the higher level, higher
|
||||
numbered modules with more dependencies listed later.
|
||||
The table below summarizes the _desired_ division of modules, based on the
|
||||
state of the rippled code when it was created. The levels are numbered from
|
||||
the bottom up with the lower level, lower numbered, more independent
|
||||
modules listed first, and the higher level, higher numbered modules with
|
||||
more dependencies listed later.
|
||||
|
||||
**tl;dr:** The modules listed first are more independent than the modules
|
||||
listed later.
|
||||
|
||||
| Level / Tier | Module(s) |
|
||||
|--------------|-----------------------------------------------|
|
||||
|
||||
Reference in New Issue
Block a user