You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For ease of review, this issue will be resolved via a series of PRs, each focusing on a section of the codebase. Once all the checks are in place an eslint rule can be placed at the top level. In the meantime, eslint rules can be introduced in sub directories to ensure compliance in the meantime.
src/core_plugins/kibana/public
ui/public/
ui/public/agg_response/*
ui/public/courier/*
ui/public/A - M
ui/public/N - Z
The rest. :)
The text was updated successfully, but these errors were encountered:
Not being actively worked on anymore. @spalger I seem to recall you recently opened up an issue to turn on a lint rule for default exports. Am I imagining that? If we have that issue, we can close this one.
This is a meta issue to track the gradual and eventual removal of default exports from all code under this repository. This will bring the code in compliance with https://github.com/elastic/kibana/blob/master/style_guides/js_style_guide.md#use-named-exports-only.
For ease of review, this issue will be resolved via a series of PRs, each focusing on a section of the codebase. Once all the checks are in place an eslint rule can be placed at the top level. In the meantime, eslint rules can be introduced in sub directories to ensure compliance in the meantime.
src/core_plugins/kibana/public
ui/public/
ui/public/agg_response/*
ui/public/courier/*
ui/public/A - M
ui/public/N - Z
The text was updated successfully, but these errors were encountered: