Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 legacy plugins support #77599
Remove legacy plugins support #77599
Changes from 27 commits
0ac0df2
67b4d8a
1f8249b
4a8c362
28db307
5e76aeb
aa4de2b
f721040
2361249
e6fb281
8467833
982494e
7363722
75a1a47
1498f79
719280a
5e5b448
1a10e3b
c5d7612
462388a
a20cc66
6be4612
8443d96
eced562
60e6963
14569f0
90e5073
beed1f9
59572bc
6ba8682
7e4a35b
91d2a6b
a570f53
ccf62c7
18bb41c
ca6412c
7c54be0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this rule makes any sense without any legacy plugin. I changed
pluginMap
to{}
, but should I just remove the whole rule instead @elastic/kibana-operations ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that the custom eslint-import-resolver-kibana settings for x-pack are only required for the legacy import syntax support for things like
ui/*
andplugins/*
. I suspect that x-pack can use the root settings and we can get rid of these settings.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't it mean that we can remove the
eslint-import-resolver-kibana
plugin at all?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually still necessary. See https://github.com/elastic/kibana/pull/77599/checks?check_run_id=1147976384
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There shouldn't be any plugin code relying on the Hapi types. Created #77997
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was only used to specify the legacy xpack plugin's path. KP's xpack path is handled in
packages/kbn-config/src/env.ts