Rename Resolver types to include 'Resolver'#69926
Conversation
|
Pinging @elastic/endpoint-app-team (Feature:Endpoint) |
There was a problem hiding this comment.
❔ 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.
There was a problem hiding this comment.
Few thoughts here:
- 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.
- 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.
- 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.
- 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.
jonathan-buttner
left a comment
There was a problem hiding this comment.
Changing the names is fine with me. We'll need to update the api_integration tests as well:
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 |
Include the word 'Resolver' in some Resolver specific types in order to improve readability and ease of auto-importing.
d781b0c to
56309a0
Compare
yah, i just goofed lol |
💚 Build SucceededBuild metricspage load asset sizebeta
History
To update your PR or re-run it, just comment with: |
Include the word 'Resolver' in some Resolver specific types in order to improve readability and ease of auto-importing.
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