Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
discourse/jsconfig.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

133 lines
4.8 KiB
JSON
Raw Permalink Normal View History

DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
// This file was generated by scripts/build_jsconfig.rb
{
"compilerOptions": {
"target": "es2021",
"module": "esnext",
"moduleResolution": "bundler",
"experimentalDecorators": true,
"paths": {
"discourse/*": [
"./app/assets/javascripts/discourse/app/*"
],
"discourse/tests/*": [
"./app/assets/javascripts/discourse/tests/*"
],
"discourse-common/*": [
"./app/assets/javascripts/discourse-common/addon/*"
],
"admin/*": [
"./app/assets/javascripts/admin/addon/*"
],
"pretty-text/*": [
"./app/assets/javascripts/pretty-text/addon/*"
],
"select-kit/*": [
"./app/assets/javascripts/select-kit/addon/*"
],
"float-kit/*": [
"./app/assets/javascripts/float-kit/addon/*"
],
"truth-helpers/*": [
"./app/assets/javascripts/truth-helpers/addon/*"
],
"dialog-holder/*": [
"./app/assets/javascripts/dialog-holder/addon/*"
],
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
"discourse/plugins/automation/*": [
"./plugins/automation/assets/javascripts/*",
"./plugins/automation/test/javascripts/*"
],
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"discourse/plugins/chat/*": [
"./plugins/chat/assets/javascripts/*",
"./plugins/chat/test/javascripts/*"
],
"discourse/plugins/checklist/*": [
"./plugins/checklist/assets/javascripts/*",
"./plugins/checklist/test/javascripts/*"
],
"discourse/plugins/discourse-details/*": [
"./plugins/discourse-details/assets/javascripts/*",
"./plugins/discourse-details/test/javascripts/*"
],
"discourse/plugins/discourse-lazy-videos/*": [
"./plugins/discourse-lazy-videos/assets/javascripts/*",
"./plugins/discourse-lazy-videos/test/javascripts/*"
],
"discourse/plugins/discourse-local-dates/*": [
"./plugins/discourse-local-dates/assets/javascripts/*",
"./plugins/discourse-local-dates/test/javascripts/*"
],
"discourse/plugins/discourse-narrative-bot/*": [
"./plugins/discourse-narrative-bot/assets/javascripts/*",
"./plugins/discourse-narrative-bot/test/javascripts/*"
],
"discourse/plugins/discourse-presence/*": [
"./plugins/discourse-presence/assets/javascripts/*",
"./plugins/discourse-presence/test/javascripts/*"
],
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
"discourse/plugins/footnote/*": [
"./plugins/footnote/assets/javascripts/*",
"./plugins/footnote/test/javascripts/*"
],
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"discourse/plugins/poll/*": [
"./plugins/poll/assets/javascripts/*",
"./plugins/poll/test/javascripts/*"
],
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
"discourse/plugins/spoiler-alert/*": [
"./plugins/spoiler-alert/assets/javascripts/*",
"./plugins/spoiler-alert/test/javascripts/*"
],
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"discourse/plugins/styleguide/*": [
"./plugins/styleguide/assets/javascripts/*",
"./plugins/styleguide/test/javascripts/*"
]
}
},
"include": [
"./app/assets/javascripts/discourse/app",
"./app/assets/javascripts/discourse/tests",
"./app/assets/javascripts/discourse-common/addon",
"./app/assets/javascripts/admin/addon",
"./app/assets/javascripts/pretty-text/addon",
"./app/assets/javascripts/select-kit/addon",
"./app/assets/javascripts/float-kit/addon",
"./app/assets/javascripts/truth-helpers/addon",
"./app/assets/javascripts/dialog-holder/addon",
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
"./plugins/automation/assets/javascripts",
"./plugins/automation/test/javascripts",
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"./plugins/chat/assets/javascripts",
"./plugins/chat/test/javascripts",
"./plugins/checklist/assets/javascripts",
"./plugins/checklist/test/javascripts",
"./plugins/discourse-details/assets/javascripts",
"./plugins/discourse-details/test/javascripts",
"./plugins/discourse-lazy-videos/assets/javascripts",
"./plugins/discourse-lazy-videos/test/javascripts",
"./plugins/discourse-local-dates/assets/javascripts",
"./plugins/discourse-local-dates/test/javascripts",
"./plugins/discourse-narrative-bot/assets/javascripts",
"./plugins/discourse-narrative-bot/test/javascripts",
"./plugins/discourse-presence/assets/javascripts",
"./plugins/discourse-presence/test/javascripts",
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
"./plugins/footnote/assets/javascripts",
"./plugins/footnote/test/javascripts",
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"./plugins/poll/assets/javascripts",
"./plugins/poll/test/javascripts",
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
"./plugins/spoiler-alert/assets/javascripts",
"./plugins/spoiler-alert/test/javascripts",
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
"./plugins/styleguide/assets/javascripts",
"./plugins/styleguide/test/javascripts"
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
],
"exclude": [
"app/assets/javascripts/discourse/tests/unit/utils/decorators-test.js",
DEV: Configure glint hbs checking (#29479) Check *.hbs, but skip 'standalone' template. This gives us working glint in colocated templates, without a ton of errors from the standalone templates which Glint can't map to the relevant component/controller
2024-10-30 11:44:33 -04:00
"app/assets/javascripts/discourse/tests/integration/component-templates-test.gjs"
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
],
"glint": {
"environment": [
"ember-loose",
"ember-template-imports"
DEV: Configure glint hbs checking (#29479) Check *.hbs, but skip 'standalone' template. This gives us working glint in colocated templates, without a ton of errors from the standalone templates which Glint can't map to the relevant component/controller
2024-10-30 11:44:33 -04:00
],
"checkStandaloneTemplates": false
DEV: Update jsconfig, add glint config, add basic check in CI (#28667) This switches us back to the 'unstable' version of Glint, which is 'Volar' under the covers. While it's still a work-in-progress, it already works much better for us than the 'stable' version of Glint. The CI check makes sure that we don't re-introduce any ts/glint-incompatible changes in future (e.g. object literal property decorators).
2024-10-29 12:55:31 -04:00
}
DEV: Consolidate and update jsconfig, and add types packages (#23824) These updates significantly improve IDE tooling for imports across the Discourse core codebase, and also for framework packages. The `@types/ember-*` packages are a temporary solution until we get onto Ember 5, which ships its types in the main package. The previous approach of having jsconfig files in each package directory did work, but once you start adding all the possible interlinks between them, we hit the file count limit of VSCode's tooling (because it counts every file for every jsconfig its referenced in). Having one file at the root means that a single file can apply to all core packages and plugins. Long-term, to get the same functionality for all themes/plugins, we may need to look at building/publishing a Discourse types package which can be added to theme/plugin package.json files for development purposes.
2023-10-18 07:13:20 -04:00
}