Menu

#495 Enhance '.every()' modifier

v1.1.x
closed
None
v1.1.2
New Functionality
2021-07-06
2019-11-17
Erik Hänel
No

The .every() modifier of table MAFs should be enhanced, to allow selections of opposite directions and finer control over which items are selected, e.g. via a passed index vector like .every({a:b:c}).

Analysis:

This functionality enhancement can be implemented, if the return value of the Datafile::parseEvery() member function is changed to a VectorIndex class instance. The function shall be enabled to parse something like {a:b:c}. This will require that all MAF implementations are changed to make use of VectorIndex class instances.

Implementation:

  • Implementation: The implementation was processed as indicated by the analysis.
  • Revision: [r738]
  • Implementation test: Different vectors and usual calls to .every() were processed successfully.

Documentation:

  • [x] ChangesLog updated
  • [x] Code changes commented
  • Documentation articles:
    • [x] corresponding documentation articles updated
    • [ ] new documentation articles created
    • [ ] not needed
  • Language files:
    • [x] corresponding language files updated
    • [ ] not needed

Tests:

Functionality was tested with the automatic SW tests. No deviations detected.

Related

Commit: [r738]
Tickets: #523

Discussion

  • Erik Hänel

    Erik Hänel - 2020-06-08
    • status: open --> accepted
     
  • Erik Hänel

    Erik Hänel - 2020-06-08
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1,23 @@
     The `.every()` modifier of table MAFs should be enhanced, to allow selections of opposite directions and finer control over which items are selected, e.g. via a passed index vector like `.every({a:b:c})`.
    +
    +###Analysis:
    +(*Describe, what's the issue and which changes have to be made*)
    +
    +###Implementation:
    +* Implementation: (*Describe, what you've changed*) 
    +* Revision: [rXXX]
    +* Implementation test: (*Describe the type of test, which you performed, and if it was successful*)
    +
    +###Documentation:
    +* [ ] ChangesLog updated
    +* [ ] Code changes commented
    +* **Documentation articles:**
    
    +    * [ ] corresponding documentation articles updated
    +    * [ ] new documentation articles created
    +    * [ ] not needed
    +* **Language files:**
    +    * [ ] corresponding language files updated
    +    * [ ] not needed
    +
    +###Tests:
    +(*Describe, which tests you performed and their outcome*)
    
    • status: accepted --> analyzing
     
  • Erik Hänel

    Erik Hänel - 2020-06-08
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,7 +1,7 @@
     The `.every()` modifier of table MAFs should be enhanced, to allow selections of opposite directions and finer control over which items are selected, e.g. via a passed index vector like `.every({a:b:c})`.
    
     ###Analysis:
    -(*Describe, what's the issue and which changes have to be made*)
    +This functionality enhancement can be implemented, if the return value of the `Datafile::parseEvery()` member function is changed to a `VectorIndex` class instance. The function shall be enabled to parse something like `{a:b:c}`. This will require that all MAF implementations are changed to make use of `VectorIndex` class instances.
    
     ###Implementation:
    
     * Implementation: (*Describe, what you've changed*) 
    
    • status: analyzing --> implementing
     
  • Erik Hänel

    Erik Hänel - 2020-06-09
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -4,19 +4,19 @@
     This functionality enhancement can be implemented, if the return value of the `Datafile::parseEvery()` member function is changed to a `VectorIndex` class instance. The function shall be enabled to parse something like `{a:b:c}`. This will require that all MAF implementations are changed to make use of `VectorIndex` class instances.
    
     ###Implementation:
    -* Implementation: (*Describe, what you've changed*) 
    -* Revision: [rXXX]
    -* Implementation test: (*Describe the type of test, which you performed, and if it was successful*)
    +* Implementation: The implementation was processed as indicated by the analysis.
    +* Revision: [r738]
    +* Implementation test: Different vectors and usual calls to `.every()` were processed successfully.
    
     ###Documentation:
    -* [ ] ChangesLog updated
    -* [ ] Code changes commented
    +* [x] ChangesLog updated
    +* [x] Code changes commented
    
     * **Documentation articles:**
    -    * [ ] corresponding documentation articles updated
    +    * [x] corresponding documentation articles updated
         * [ ] new documentation articles created
         * [ ] not needed
     * **Language files:**
    -    * [ ] corresponding language files updated
    +    * [x] corresponding language files updated
         * [ ] not needed
    
     ###Tests:
    
    • status: implementing --> testing
     

    Related

    Commit: [r738]

  • Erik Hänel

    Erik Hänel - 2020-11-02
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -20,4 +20,4 @@
    
         * [ ] not needed
    
     ###Tests:
    -(*Describe, which tests you performed and their outcome*)
    +Functionality was tested with the automatic SW tests. No deviations detected.
    
    • status: testing --> closed
     
  • Erik Hänel

    Erik Hänel - 2021-07-06
    • Version: Planned --> v1.1.2
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB