-
Notifications
You must be signed in to change notification settings - Fork 50
fix: prevent publish test-workspaces W-19605327 #624
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -24,3 +24,4 @@ npm-debug.log | |
| *.tgz | ||
| .npmrc | ||
| package-lock.json | ||
| core.code-workspace | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,28 @@ | ||
| # Dev config folders | ||
| /.circleci | ||
| /.vscode | ||
| /coverage | ||
| /jest | ||
| /scripts | ||
| /src | ||
| /test-workspaces | ||
| /typings | ||
| **/__tests__/** | ||
| .circleci/ | ||
| .vscode/ | ||
| coverage/ | ||
| jest/ | ||
| scripts/ | ||
| src/ | ||
| test-workspaces/ | ||
| typings/ | ||
| **/__tests__/ | ||
|
|
||
| # Configuration files | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .huskyrc | ||
| .lintstagedrc | ||
| .prettierrc | ||
| copy-static-assets.ts | ||
| jest.config.js | ||
| jest.setup.js | ||
| tsconfig.json | ||
| tslint.json | ||
|
|
||
| # Development files | ||
| core.code-workspace | ||
|
|
||
| # Ignore artifacts | ||
| *.tgz |
This file was deleted.
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -38,6 +38,6 @@ | |||||
| "extensions.ignoreRecommendations": true, | ||||||
| "salesforcedx-vscode-lightning.activationMode": "always", | ||||||
| "salesforcedx-vscode-lightning.showLightningExplorer": true, | ||||||
| "salesforcedx-vscode-core.internal-development": true | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. are these sneaking in from writing base-context? lightning-language-server/packages/lightning-lsp-common/src/base-context.ts Lines 261 to 262 in aaadd02
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. maybe we're missing some kind of check to verify that you're working in the salesforce internal repo that all this supports?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the big problem with making changes is that we don't test that scenario at all (using ext for internal development) but there's probably users that need it. |
||||||
| "salesforcedx-vscode-core.internal-development": false | ||||||
| } | ||||||
| } | ||||||
This file was deleted.
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.
Huh. We don't normally use
npmignore. The normal approach is to have afilesproperty on the package.json that says what files go in, instead of trying to explicitly ignore files.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.
ex: https://github.com/forcedotcom/sfdx-core/blob/69c0055e7303decdc6d4d79d4ea1944f7e90287a/package.json#L50
I'd rather have "e2e failed because you forgot to put something in
package.json#files" rather than, "you accidentally package unnecessary stuff because you didn't put it in the.npmignorefile"