Skip to content
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

[ts/checkProjects] validate extends of all ts projects #145176

Merged
merged 3 commits into from
Nov 16, 2022

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Nov 14, 2022

Fixes #145129

In order to make our TS setup in the repo far more efficient we needed to make it a little more complicated than it used to be. This includes a few rules that all tsconfig files need to follow which were currently assumed to be true, but with this PR will now be validated:

  1. No tsconfig.json files are allowed to extend the tsconfig.json file. This file is used to produce types for the root of the repo, and include the package.json file in a project so it can be referenced in projects directly. Files which violate this rule were updated to point to the root tsconfig.base.json file.
  2. Every tsconfig.json file must extend the tsconfig.base.json file, either directly or indirectly.

@spalger spalger added Team:Operations Team label for Operations Team release_note:skip Skip the PR/issue when compiling release notes labels Nov 14, 2022
@kibana-ci
Copy link
Collaborator

kibana-ci commented Nov 14, 2022

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Unknown metric groups

ESLint disabled in files

id before after diff
osquery 1 2 +1

ESLint disabled line counts

id before after diff
enterpriseSearch 19 21 +2
fleet 59 65 +6
osquery 108 113 +5
securitySolution 441 447 +6
total +19

Total ESLint disabled count

id before after diff
enterpriseSearch 20 22 +2
fleet 67 73 +6
osquery 109 115 +6
securitySolution 518 524 +6
total +20

History

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

@spalger spalger marked this pull request as ready for review November 14, 2022 22:15
@spalger spalger requested review from a team as code owners November 14, 2022 22:15
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

Copy link
Contributor

@Dosant Dosant left a comment

Choose a reason for hiding this comment

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

Thank you 🙏

@spalger spalger merged commit 12aeaa8 into elastic:main Nov 16, 2022
@spalger spalger deleted the implement/basic-ts-project-validation branch November 16, 2022 15:57
@kibanamachine kibanamachine added v8.6.0 backport:skip This commit does not require backporting labels Nov 16, 2022
benakansara pushed a commit to benakansara/kibana that referenced this pull request Nov 17, 2022
Fixes elastic#145129

In order to make our TS setup in the repo far more efficient we needed
to make it a little more complicated than it used to be. This includes a
few rules that all tsconfig files need to follow which were currently
assumed to be true, but with this PR will now be validated:

1. No tsconfig.json files are allowed to extend the `tsconfig.json`
file. This file is used to produce types for the root of the repo, and
include the `package.json` file in a project so it can be referenced in
projects directly. Files which violate this rule were updated to point
to the root `tsconfig.base.json` file.
2. Every tsconfig.json file must extend the `tsconfig.base.json` file,
either directly or indirectly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v8.6.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

node scripts/type_check.js doesn't work for example plugins
9 participants