Skip to content
This repository was archived by the owner on Oct 14, 2020. It is now read-only.

Commit eb0d1d0

Browse files
committed
#30 Remove redundnat text
By the ordered lists numbers it became obvious that they are questioon one and two. Signed-off-by: Sven Strittmatter <sven.strittmatter@iteratec.com>
1 parent c3dd853 commit eb0d1d0

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

docs/adr/adr_0001.adoc

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,11 +39,10 @@ By now the "Persisting Phase 3" was implemented by so called _persistenceProvide
3939

4040
We identified different additional UseCases with a more _data proccessing oriented_ pattern than the implemented _persisting phase3_ indicates. For example, we implemented a so called "MetaDataProvider" feature, which is responsible for enhancing each security finding with additional metadata. But the MetaDataProvider must be executed after the _parsing phase 2_ and before the _persisting phase 3_ because it depends on the parsed finding results (which will be enhanced) and the update findings should be also persisted.
4141

42-
4342
To find a proper solution, we splitted the topic into the follwong two questions:
4443

45-
. Question 1: Should we unify the concepts MetaDataProvider and PersistenceProvider?
46-
. Question 2: How should the execution model look like for each concept?
44+
. Should we unify the concepts MetaDataProvider and PersistenceProvider?
45+
. How should the execution model look like for each concept?
4746

4847
==== Question 1: Should we unify the concepts MetaDataProvider and PersistenceProvider?
4948

0 commit comments

Comments
 (0)