-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Remove references to ReportingCore from Export Type code #158092
Labels
Team:SharedUX
Team label for AppEx-SharedUX (formerly Global Experience)
Comments
1 task
petrklapka
added
the
Team:SharedUX
Team label for AppEx-SharedUX (formerly Global Experience)
label
May 18, 2023
Pinging @elastic/appex-sharedux (Team:SharedUX) |
rshen91
added a commit
that referenced
this issue
May 22, 2023
## Summary Part of #158092 Removing calls to `ReportingCore` in export types functions ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
This was referenced May 22, 2023
delanni
pushed a commit
to delanni/kibana
that referenced
this issue
May 25, 2023
## Summary Part of elastic#158092 Removing calls to `ReportingCore` in export types functions ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
This was referenced May 31, 2023
This was referenced Jun 15, 2023
rshen91
added a commit
that referenced
this issue
Jun 27, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jun 28, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
to rshen91/kibana
that referenced
this issue
Jun 30, 2023
## Summary This partially addresses elastic#158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 5, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
to rshen91/kibana
that referenced
this issue
Jul 5, 2023
This partially addresses elastic#158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function. [CI] Auto-commit changed files from 'node scripts/lint_ts_projects --fix' update imports
rshen91
added a commit
that referenced
this issue
Jul 6, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 6, 2023
## Summary This is a part of #158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 10, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 10, 2023
## Summary This is a part of #158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 11, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 11, 2023
## Summary This is a part of #158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 12, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 12, 2023
## Summary This is a part of #158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 12, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 12, 2023
## Summary This is a part of #158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 12, 2023
## Summary Partially addresses #158092 Following the Csv and Pdf reports, this PR continues the process with a PngExportType class instance vs the getExportType() function. This PR concludes refactoring the export types to class instances. The next steps will be migrating these to the reporting export types plugin #161291 and clean up of tests. Diagnostic tool is timing out for waitForElements - in this PR this is commented out since the png v1 endpoint has not been refactored yet. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 13, 2023
## Summary This partially addresses #158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
that referenced
this issue
Jul 13, 2023
## Summary This is a part of #158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
that referenced
this issue
Jul 13, 2023
## Summary Partially addresses #158092 Following the Csv and Pdf reports, this PR continues the process with a PngExportType class instance vs the getExportType() function. This PR concludes refactoring the export types to class instances. The next steps will be migrating these to the reporting export types plugin #161291 and clean up of tests. Diagnostic tool is timing out for waitForElements - in this PR this is commented out since the png v1 endpoint has not been refactored yet. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
to rshen91/kibana
that referenced
this issue
Jul 20, 2023
## Summary This partially addresses elastic#158092 This PR refactors the generic function getExportType(). This PR is concerned only with the PDF export type and refactors it into a class instance. This class is then used in the request handler and the execute report functionality in Reporting. The execute_report.test.ts is removed in this PR and will be part of the clean up needed in a subsequent PR once CSV and PNG are also refactored to class instances instead of the getExportType() function.
rshen91
added a commit
to rshen91/kibana
that referenced
this issue
Jul 20, 2023
## Summary This is a part of elastic#158092 This PR encompasses both csv_v2 and csv_searchsource as the CsvExportType and CsvSearchsourceExportType. Based on the reporting plugin readme, CsvSearchsourceExportType is currently used but CsvV2ExportType is refactored for when it can reach feature parity to csv searchsource. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
rshen91
added a commit
to rshen91/kibana
that referenced
this issue
Jul 20, 2023
## Summary Partially addresses elastic#158092 Following the Csv and Pdf reports, this PR continues the process with a PngExportType class instance vs the getExportType() function. This PR concludes refactoring the export types to class instances. The next steps will be migrating these to the reporting export types plugin elastic#161291 and clean up of tests. Diagnostic tool is timing out for waitForElements - in this PR this is commented out since the png v1 endpoint has not been refactored yet. ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Timothy Sullivan <[email protected]>
This issue is completed 🥳 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code in
x-pack/plugins/reporting/server/export_types
is planned to be removed from the reporting plugin and relocated into a new standalone plugin.A large challenge with this task is to remove references to the
ReportingCore
object in that code. In the new destination plugin for the export types, there will not be theReportingCore
.Affected code
Colorized version:
A common approach for removing ReportingCore references from
execute_job
andcreate_job
functions.Reporting export types should be redesigned. Today, they are plain objects with stateless functions. They get
state from having the ReportingCore object passed in. By redesigning them as class instances, they can be
constructed with a "fresh" state that isn't dependent on ReportingCore. They can also have lifecycle methods to
receive stateful dependencies from the
setup
andstart
phases.getExportTypesRegistry
function.class:
The text was updated successfully, but these errors were encountered: