Skip to content

Rename Resolver types to include 'Resolver'#69926

Merged
oatkiller merged 1 commit intoelastic:masterfrom
oatkiller:renaming-resolver-types
Jun 25, 2020
Merged

Rename Resolver types to include 'Resolver'#69926
oatkiller merged 1 commit intoelastic:masterfrom
oatkiller:renaming-resolver-types

Conversation

@oatkiller
Copy link
Copy Markdown
Contributor

Summary

Include the word 'Resolver' in some Resolver specific types in order to improve readability and ease of auto-importing.

I found that this made it easier for me to read and understand some code while working on #69728

Checklist

Delete any items that are not applicable to this PR.

For maintainers

@oatkiller oatkiller requested review from a team as code owners June 25, 2020 13:33
@oatkiller oatkiller added Feature:Endpoint Elastic Endpoint feature release_note:skip Skip the PR/issue when compiling release notes v7.9.0 labels Jun 25, 2020
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/endpoint-app-team (Feature:Endpoint)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❔ I've been trying to stop saying "Resolver" as much in favor of "GTV", I know they are changing the name for this officially, so it might be worth asking when we stop calling it that in our code? I'm not suggesting "right here, right now" just want to flag the issue.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few thoughts here:

  1. I think that naming a project too early can be dangerous. If the scope and definition of a project is complete (won't change ever again), then naming it in a way that describes what it does is fine. But if you rename something like Resolver to 'Graphical Timeline', then people start thinking 'oh we should do A because this is a graphical timeline', or 'we shouldn't do b, because that doesn't fit the description of a graphical timeline.' Resolver isn't mature and its definition is going to be changing every release.
  2. I'm hoping that this project isn't always specific to Security Solution. 'Graphical Timeline' is a branding term for a specific feature in Security Solution. That feature uses Resolver, but Resolver might be used elsewhere for other things. In other words, I'm thinking of Resolver as the mapping/graphing technology.
  3. If the term Graphical Timeline sticks around long enough that there becomes confusion, then we should reconsider the name of the project. I'm in a meeting right now and I've heard 'Resolver' said many times.
  4. Graphical Timeline is an awkward name for a code project. Having a generic and vague name might be good for branding, but it would probably be confusing in our code base. For one thing, Resolver is entirely unrelated to Timeline, which is also a project in Security Solution.

Copy link
Copy Markdown
Contributor

@jonathan-buttner jonathan-buttner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the names is fine with me. We'll need to update the api_integration tests as well:

https://github.com/elastic/kibana/blob/master/x-pack/test/api_integration/apis/endpoint/resolver.ts#L9

@oatkiller
Copy link
Copy Markdown
Contributor Author

Changing the names is fine with me. We'll need to update the api_integration tests as well:

https://github.com/elastic/kibana/blob/master/x-pack/test/api_integration/apis/endpoint/resolver.ts#L9

I'm curious why this isn't failing typecheck (locally at least.) I'm going to wait and see what happens on CI.

@jonathan-buttner
Copy link
Copy Markdown
Contributor

Changing the names is fine with me. We'll need to update the api_integration tests as well:
https://github.com/elastic/kibana/blob/master/x-pack/test/api_integration/apis/endpoint/resolver.ts#L9

I'm curious why this isn't failing typecheck (locally at least.) I'm going to wait and see what happens on CI.

Looks like it failed in CI: https://github.com/elastic/kibana/pull/69926/checks?check_run_id=807607380

That is odd that it didn't fail locally 🤔 I wonder if the x-pack/tests directory isn't scanned?

Include the word 'Resolver' in some Resolver specific types in order to
improve readability and ease of auto-importing.
@oatkiller oatkiller force-pushed the renaming-resolver-types branch from d781b0c to 56309a0 Compare June 25, 2020 15:24
@oatkiller
Copy link
Copy Markdown
Contributor Author

Changing the names is fine with me. We'll need to update the api_integration tests as well:
https://github.com/elastic/kibana/blob/master/x-pack/test/api_integration/apis/endpoint/resolver.ts#L9

I'm curious why this isn't failing typecheck (locally at least.) I'm going to wait and see what happens on CI.

Looks like it failed in CI: https://github.com/elastic/kibana/pull/69926/checks?check_run_id=807607380

That is odd that it didn't fail locally 🤔 I wonder if the x-pack/tests directory isn't scanned?

yah, i just goofed lol

@kibanamachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Build metrics

page load asset size

beta
id value diff baseline
/bundles/app/core/bootstrap.js - -13.8KB 13.8KB
/bundles/core/core.entry.js - -1.1MB 1.1MB
/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.@elastic.js - -4.0MB 4.0MB
/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.css - -183.7KB 183.7KB
/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js - -4.6MB 4.6MB
/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.v7.light.css - -511.3KB 511.3KB
/bundles/light_theme.style.css - -95.9KB 95.9KB
/bundles/plugin/advancedSettings/advancedSettings.plugin.js - -941.3KB 941.3KB
/bundles/plugin/alerts/alerts.plugin.js - -89.5KB 89.5KB
/bundles/plugin/apm/apm.plugin.js - -215.2KB 215.2KB
/bundles/plugin/apmOss/apmOss.plugin.js - -4.2KB 4.2KB
/bundles/plugin/beats_management/beats_management.plugin.js - -522.9KB 522.9KB
/bundles/plugin/bfetch/bfetch.plugin.js - -28.7KB 28.7KB
/bundles/plugin/canvas/canvas.plugin.js - -2.0MB 2.0MB
/bundles/plugin/charts/charts.plugin.js - -833.9KB 833.9KB
/bundles/plugin/cloud/cloud.plugin.js - -6.3KB 6.3KB
/bundles/plugin/console/console.plugin.js - -28.0KB 28.0KB
/bundles/plugin/crossClusterReplication/crossClusterReplication.plugin.js - -152.3KB 152.3KB
/bundles/plugin/dashboard/dashboard.plugin.js - -634.0KB 634.0KB
/bundles/plugin/dashboardEnhanced/dashboardEnhanced.plugin.js - -143.5KB 143.5KB
/bundles/plugin/dashboardMode/dashboardMode.plugin.js - -109.3KB 109.3KB
/bundles/plugin/data/data.plugin.js - -1.3MB 1.3MB
/bundles/plugin/dataEnhanced/dataEnhanced.plugin.js - -138.1KB 138.1KB
/bundles/plugin/devTools/devTools.plugin.js - -123.9KB 123.9KB
/bundles/plugin/discover/discover.plugin.js - -221.1KB 221.1KB
/bundles/plugin/discoverEnhanced/discoverEnhanced.plugin.js - -13.8KB 13.8KB
/bundles/plugin/embeddable/embeddable.plugin.js - -387.2KB 387.2KB
/bundles/plugin/embeddableEnhanced/embeddableEnhanced.plugin.js - -26.3KB 26.3KB
/bundles/plugin/esUiShared/esUiShared.plugin.js - -927.8KB 927.8KB
/bundles/plugin/expressions/expressions.plugin.js - -314.9KB 314.9KB
/bundles/plugin/features/features.plugin.js - -13.4KB 13.4KB
/bundles/plugin/fileUpload/fileUpload.plugin.js - -688.0KB 688.0KB
/bundles/plugin/globalSearch/globalSearch.plugin.js - -29.0KB 29.0KB
/bundles/plugin/graph/graph.plugin.js - -15.3KB 15.3KB
/bundles/plugin/grokdebugger/grokdebugger.plugin.js - -11.2KB 11.2KB
/bundles/plugin/home/home.plugin.js - -24.6KB 24.6KB
/bundles/plugin/indexLifecycleManagement/indexLifecycleManagement.plugin.js - -184.2KB 184.2KB
/bundles/plugin/indexManagement/indexManagement.plugin.js - -201.7KB 201.7KB
/bundles/plugin/indexPatternManagement/indexPatternManagement.plugin.js - -137.3KB 137.3KB
/bundles/plugin/infra/infra.plugin.js - -92.9KB 92.9KB
/bundles/plugin/ingestPipelines/ingestPipelines.plugin.js - -30.3KB 30.3KB
/bundles/plugin/inputControlVis/inputControlVis.plugin.js - -258.9KB 258.9KB
/bundles/plugin/inspector/inspector.plugin.js - -238.3KB 238.3KB
/bundles/plugin/kibanaLegacy/kibanaLegacy.plugin.js - -174.7KB 174.7KB
/bundles/plugin/kibanaReact/kibanaReact.plugin.js - -575.3KB 575.3KB
/bundles/plugin/kibanaUtils/kibanaUtils.plugin.js - -432.8KB 432.8KB
/bundles/plugin/lens/lens.plugin.js - -746.9KB 746.9KB
/bundles/plugin/licenseManagement/licenseManagement.plugin.js - -26.2KB 26.2KB
/bundles/plugin/licensing/licensing.plugin.js - -21.6KB 21.6KB
/bundles/plugin/logstash/logstash.plugin.js - -141.8KB 141.8KB
/bundles/plugin/management/management.plugin.js - -25.9KB 25.9KB
/bundles/plugin/maps/maps.plugin.js - -220.0KB 220.0KB
/bundles/plugin/mapsLegacy/mapsLegacy.plugin.js - -1.0MB 1.0MB
/bundles/plugin/mapsLegacyLicensing/mapsLegacyLicensing.plugin.js - -3.9KB 3.9KB
/bundles/plugin/ml/ml.plugin.js - -1.3MB 1.3MB
/bundles/plugin/monitoring/monitoring.plugin.js - -22.8KB 22.8KB
/bundles/plugin/navigation/navigation.plugin.js - -122.2KB 122.2KB
/bundles/plugin/newsfeed/newsfeed.plugin.js - -22.7KB 22.7KB
/bundles/plugin/observability/observability.plugin.js - -103.3KB 103.3KB
/bundles/plugin/painlessLab/painlessLab.plugin.js - -158.8KB 158.8KB
/bundles/plugin/regionMap/regionMap.plugin.js - -791.7KB 791.7KB
/bundles/plugin/remoteClusters/remoteClusters.plugin.js - -35.2KB 35.2KB
/bundles/plugin/reporting/reporting.plugin.js - -257.7KB 257.7KB
/bundles/plugin/rollup/rollup.plugin.js - -186.0KB 186.0KB
/bundles/plugin/savedObjects/savedObjects.plugin.js - -196.2KB 196.2KB
/bundles/plugin/savedObjectsManagement/savedObjectsManagement.plugin.js - -176.6KB 176.6KB
/bundles/plugin/searchprofiler/searchprofiler.plugin.js - -42.8KB 42.8KB
/bundles/plugin/security/security.plugin.js - -248.0KB 248.0KB
/bundles/plugin/share/share.plugin.js - -80.5KB 80.5KB
/bundles/plugin/snapshotRestore/snapshotRestore.plugin.js - -57.5KB 57.5KB
/bundles/plugin/spaces/spaces.plugin.js - -367.3KB 367.3KB
/bundles/plugin/statusPage/statusPage.plugin.js - -3.6KB 3.6KB
/bundles/plugin/telemetry/telemetry.plugin.js - -77.2KB 77.2KB
/bundles/plugin/telemetryManagementSection/telemetryManagementSection.plugin.js - -27.5KB 27.5KB
/bundles/plugin/tileMap/tileMap.plugin.js - -807.1KB 807.1KB
/bundles/plugin/transform/transform.plugin.js - -21.6KB 21.6KB
/bundles/plugin/triggers_actions_ui/triggers_actions_ui.plugin.js - -102.9KB 102.9KB
/bundles/plugin/uiActions/uiActions.plugin.js - -162.5KB 162.5KB
/bundles/plugin/uiActionsEnhanced/uiActionsEnhanced.plugin.js - -124.1KB 124.1KB
/bundles/plugin/upgradeAssistant/upgradeAssistant.plugin.js - -46.6KB 46.6KB
/bundles/plugin/uptime/uptime.plugin.js - -327.3KB 327.3KB
/bundles/plugin/usageCollection/usageCollection.plugin.js - -24.4KB 24.4KB
/bundles/plugin/visTypeMarkdown/visTypeMarkdown.plugin.js - -512.5KB 512.5KB
/bundles/plugin/visTypeMetric/visTypeMetric.plugin.js - -536.7KB 536.7KB
/bundles/plugin/visTypeTable/visTypeTable.plugin.js - -563.0KB 563.0KB
/bundles/plugin/visTypeTagcloud/visTypeTagcloud.plugin.js - -797.1KB 797.1KB
/bundles/plugin/visTypeTimelion/visTypeTimelion.plugin.js - -670.7KB 670.7KB
/bundles/plugin/visTypeTimeseries/visTypeTimeseries.plugin.js - -212.2KB 212.2KB
/bundles/plugin/visTypeVega/visTypeVega.plugin.js - -580.3KB 580.3KB
/bundles/plugin/visTypeVislib/visTypeVislib.plugin.js - -1.2MB 1.2MB
/bundles/plugin/visualizations/visualizations.plugin.js - -343.4KB 343.4KB
/bundles/plugin/visualize/visualize.plugin.js - -18.2KB 18.2KB
/bundles/plugin/watcher/watcher.plugin.js - -35.2KB 35.2KB
/node_modules/@kbn/ui-framework/dist/kui_light.css - -62.1KB 62.1KB
/translations/en.json - -29.0B 29.0B
/ui/fonts/inter_ui/Inter-UI-Medium.woff2 - -92.2KB 92.2KB
/ui/fonts/inter_ui/Inter-UI-Regular.woff2 - -86.4KB 86.4KB
total - -36.1MB -

History

  • 💔 Build #56300 failed d781b0c85b7fd804f2ce5176f5d4b76aa3c740c4

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@oatkiller oatkiller merged commit c7aec6e into elastic:master Jun 25, 2020
@oatkiller oatkiller deleted the renaming-resolver-types branch June 25, 2020 18:54
oatkiller pushed a commit to oatkiller/kibana that referenced this pull request Jun 25, 2020
Include the word 'Resolver' in some Resolver specific types in order to
improve readability and ease of auto-importing.
oatkiller pushed a commit that referenced this pull request Jun 25, 2020
Include the word 'Resolver' in some Resolver specific types in order to
improve readability and ease of auto-importing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature:Endpoint Elastic Endpoint feature release_note:skip Skip the PR/issue when compiling release notes v7.9.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants