Project

General

Profile

Feature #8418

Feature #8416: Suggest better file archives passing from Core to Bridge

Support more flexible file archives passing

Added by Evgeny Novikov about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Urgent
Category:
-
Target version:
Start date:
09/08/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

See the description and comments in #8416.

Indeed there are many places in different components that should be changed after this. Ideally I would like to merge a great refactoring of Core before this issue to reduce an overhead.


Related issues

Blocked by Klever - Feature #7800: Refactoring of VTGClosed12/13/2016

Actions

History

#1

Updated by Evgeny Novikov about 3 years ago

I suppose to support the high-level interface for reporting file archives in different Core components, e.g. the following fragment can be a part of a report:

"attr": {
  "subattr1": ReportFiles(["subattr1/path/to/file1", "subattr1/path/to/file2", ...]),
  "subattr2": [
    ReportFiles(["subattr2/path/to/file1", "subattr2/path/to/file2", ...]),
    ReportFiles(["subattr2/path/to/fileZ", "subattr2/path/to/fileY", ...]),
    ReportFiles(["subattr2/path/to/fileA", "subattr2/path/to/fileB", ...])
  ]
}

#2

Updated by Evgeny Novikov about 3 years ago

Don't forget to rebase it on top of the latest master.

#3

Updated by Alexey Polushkin almost 3 years ago

  • Status changed from New to Resolved

Resolved in 'new_report_archives' branch.

#4

Updated by Evgeny Novikov almost 3 years ago

  • Status changed from Resolved to Closed

I merged the branch that has this feature (multicoverage) to master in 37f0c082.

Also available in: Atom PDF