Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Externalize exports #19

Closed
WaldoFR opened this issue May 10, 2017 · 0 comments
Closed

Externalize exports #19

WaldoFR opened this issue May 10, 2017 · 0 comments
Assignees
Milestone

Comments

@WaldoFR
Copy link

WaldoFR commented May 10, 2017

Inventory

Currently i-Code UI plugin is responsible of the analysis results export, the export code is included the ViolationsView and MetricsView for each formats available and the user must use dedicated Wizards hardcoded to run an export.
This design causes difficulties to add any new export format into i-Code.

Enhancement

We would like to use a dedicated and externalized export plugin to export lists of Violation and FileValue objects in some different formats plugged to the export plugin. It implies to also externalize the XML and CSV exports into two dedicated plugins.

Also, we would like also the code to be evolutionary enough to prepare i-Code import feature and include it in the modifications.

This imply both to manage :

  • The creation of a plugin dependant only of the analyzer for the analysis, and it's plugin to export in different formats
  • Modify UI to be able to use this exports

⚠️ Warning : This enhancement intended to the version 3.0 is part dependant of #16 issue progress as the Violation and FileValue classes exported in the future dedicated plugins might be merged in a common class.

@WaldoFR WaldoFR self-assigned this May 10, 2017
dupuisa added a commit that referenced this issue Jun 12, 2017
@WaldoFR WaldoFR modified the milestone: Version 3.0 Jul 5, 2017
@WaldoFR WaldoFR closed this as completed Jul 5, 2017
WaldoFR pushed a commit that referenced this issue Jul 13, 2017
LEX metric's files were edited to leave no location when computed for a
file. Also, the export Wizard is now common to both Violation & Metric
views. The service of the plugin fr.cnes.analysis.tools.export.xml was
improved to give a nameplace for method locations and only a TypePlace
for when the metric is intended to the whole file.
All test were updated to identify the CheckResult corresponding to the
old FileValue class (when no location is set).
WaldoFR pushed a commit that referenced this issue Jul 13, 2017
JDom was necessary while `MetricsView` was still using it to export XML.
Now, the view do not handle any .xml file.
WaldoFR pushed a commit that referenced this issue Jul 13, 2017
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
LEX metric's files were edited to leave no location when computed for a
file. Also, the export Wizard is now common to both Violation & Metric
views. The service of the plugin fr.cnes.analysis.tools.export.xml was
improved to give a nameplace for method locations and only a TypePlace
for when the metric is intended to the whole file.
All test were updated to identify the CheckResult corresponding to the
old FileValue class (when no location is set).
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
JDom was necessary while `MetricsView` was still using it to export XML.
Now, the view do not handle any .xml file.
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
begarco pushed a commit that referenced this issue Feb 2, 2020
LEX metric's files were edited to leave no location when computed for a
file. Also, the export Wizard is now common to both Violation & Metric
views. The service of the plugin fr.cnes.analysis.tools.export.xml was
improved to give a nameplace for method locations and only a TypePlace
for when the metric is intended to the whole file.
All test were updated to identify the CheckResult corresponding to the
old FileValue class (when no location is set).
begarco pushed a commit that referenced this issue Feb 2, 2020
JDom was necessary while `MetricsView` was still using it to export XML.
Now, the view do not handle any .xml file.
begarco pushed a commit that referenced this issue Feb 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant