Skip to content

Commit

Permalink
chore(prettier): apply fixes from version bump
Browse files Browse the repository at this point in the history
  • Loading branch information
wjhsf committed Dec 2, 2024
1 parent 4cadc59 commit e0608e6
Show file tree
Hide file tree
Showing 4 changed files with 62 additions and 62 deletions.
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,8 @@ sfdx-lwc-jest -- --no-cache

### Version

- @salesforce/sfdx-lwc-jest: x.x.x
- Node: x.x.x
- @salesforce/sfdx-lwc-jest: x.x.x
- Node: x.x.x

**Possible Solution**

Expand Down
76 changes: 38 additions & 38 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,129 +6,129 @@ Newer release notes can be found in [GitHub Releases](https://github.com/salesfo

## Fixes

- Update a variety of stubs, including adding missing `empApi` and `pageReferenceUtils` libraries [#134](https://github.com/salesforce/sfdx-lwc-jest/pull/134)
- Add `selectedItem` attribute to `<lightning-tree>` stub [#126](https://github.com/salesforce/sfdx-lwc-jest/pull/126)
- Add missing `<lightning-progress-ring>` stub [#132](https://github.com/salesforce/sfdx-lwc-jest/pull/132)
- Update a variety of stubs, including adding missing `empApi` and `pageReferenceUtils` libraries [#134](https://github.com/salesforce/sfdx-lwc-jest/pull/134)
- Add `selectedItem` attribute to `<lightning-tree>` stub [#126](https://github.com/salesforce/sfdx-lwc-jest/pull/126)
- Add missing `<lightning-progress-ring>` stub [#132](https://github.com/salesforce/sfdx-lwc-jest/pull/132)

## Chores

- Add code formatting and linting on all files [#135](https://github.com/salesforce/sfdx-lwc-jest/pull/135)
- Add code formatting and linting on all files [#135](https://github.com/salesforce/sfdx-lwc-jest/pull/135)

## 0.7.0 (January 22, 2020)

## Fixes

- Fix null exit code in jest process exit [#120](https://github.com/salesforce/sfdx-lwc-jest/pull/120)
- Fix null exit code in jest process exit [#120](https://github.com/salesforce/sfdx-lwc-jest/pull/120)

## Chores

- Upgrade LWC to version 1.1.13-224.4
- Upgrade LWC to version 1.1.13-224.4

## 0.6.2 (November 25, 2019)

## Fixes

- Add missing `required` property to `<lightning-input>` [#114](https://github.com/salesforce/sfdx-lwc-jest/pull/114)
- Add missing `required` property to `<lightning-input>` [#114](https://github.com/salesforce/sfdx-lwc-jest/pull/114)

## Chores

- Upgrade `dependencies` and `devDependencies` [#112](https://github.com/salesforce/sfdx-lwc-jest/pull/112)
- Update bin reference. The `sfdx-lwc-jest` package will now expose 2 aliases `sfdx-lwc-jest` and `lwc-jest` (legacy binary name) pointing to the same executable file. [#100](https://github.com/salesforce/sfdx-lwc-jest/pull/100)
- Upgrade `dependencies` and `devDependencies` [#112](https://github.com/salesforce/sfdx-lwc-jest/pull/112)
- Update bin reference. The `sfdx-lwc-jest` package will now expose 2 aliases `sfdx-lwc-jest` and `lwc-jest` (legacy binary name) pointing to the same executable file. [#100](https://github.com/salesforce/sfdx-lwc-jest/pull/100)

## 0.6.1 (October 16, 2019)

## Fixes

- Add missing `dateStyle` and `timeStyle` properties to `<lightning-input>` [#94](https://github.com/salesforce/sfdx-lwc-jest/pull/94)
- Add missing `autocomplete` property to `<lightning-input>` [#92](https://github.com/salesforce/sfdx-lwc-jest/pull/92)
- Add missing `dateStyle` and `timeStyle` properties to `<lightning-input>` [#94](https://github.com/salesforce/sfdx-lwc-jest/pull/94)
- Add missing `autocomplete` property to `<lightning-input>` [#92](https://github.com/salesforce/sfdx-lwc-jest/pull/92)

## Chores

- Upgrade `lwc` related packages to the latest version [#100](https://github.com/salesforce/sfdx-lwc-jest/pull/100)
- Upgrade `lwc` related packages to the latest version [#100](https://github.com/salesforce/sfdx-lwc-jest/pull/100)

## 0.5.3 (August 8, 2019)

## Chores

- Rename package to `@salesforce/sfdx-lwc-jest` to match project name [#86](https://github.com/salesforce/sfdx-lwc-jest/pull/86)
- Rename package to `@salesforce/sfdx-lwc-jest` to match project name [#86](https://github.com/salesforce/sfdx-lwc-jest/pull/86)

## 0.5.2 (August 7, 2019)

## Features

- Add real implementation to `getFieldValue` and `getFieldDisplayValue` [#83](https://github.com/salesforce/sfdx-lwc-jest/pull/83)
- Add real implementation to `getFieldValue` and `getFieldDisplayValue` [#83](https://github.com/salesforce/sfdx-lwc-jest/pull/83)

## Fixes

- Add missing `tooltip` and `density` properties to stubs [#81](https://github.com/salesforce/sfdx-lwc-jest/pull/81)
- Add missing `variant` property to `<lightning-radio-group>` [#74](https://github.com/salesforce/sfdx-lwc-jest/pull/74)
- Update code coverage paths so coverage is properly reported on Windows [#72](https://github.com/salesforce/sfdx-lwc-jest/pull/72)
- Add missing `tooltip` and `density` properties to stubs [#81](https://github.com/salesforce/sfdx-lwc-jest/pull/81)
- Add missing `variant` property to `<lightning-radio-group>` [#74](https://github.com/salesforce/sfdx-lwc-jest/pull/74)
- Update code coverage paths so coverage is properly reported on Windows [#72](https://github.com/salesforce/sfdx-lwc-jest/pull/72)

## Chores

- Upgrade `js-yaml` dependency to address security alert [#82](https://github.com/salesforce/sfdx-lwc-jest/pull/82)
- Upgrade `lodash` dependency to address security alert [#78](https://github.com/salesforce/sfdx-lwc-jest/pull/78)
- Upgrade `js-yaml` dependency to address security alert [#82](https://github.com/salesforce/sfdx-lwc-jest/pull/82)
- Upgrade `lodash` dependency to address security alert [#78](https://github.com/salesforce/sfdx-lwc-jest/pull/78)

## 0.5.1 (June 18, 2019)

### Fixes

- Add `title` property back to the `<lightning-card>` stub ([#69](https://github.com/salesforce/lwc-jest/pull/69))
- Add `title` property back to the `<lightning-card>` stub ([#69](https://github.com/salesforce/lwc-jest/pull/69))

### Chores

- Upgrade LWC to version 0.37.4-220.2, removes `deasync` dependency :tada:
- Upgrade LWC to version 0.37.4-220.2, removes `deasync` dependency :tada:

## 0.5.0 (May 13, 2019)

### Fixes

- `platformResourceLoader` mock returns resolved Promise again
- `platformResourceLoader` mock returns resolved Promise again

### Chores

- Upgrade LWC to version 0.37.4
- Expected API version check bumped to version 46.0 to match next major release
- Upgrade Jest to version 24.8.0
- Upgrade LWC to version 0.37.4
- Expected API version check bumped to version 46.0 to match next major release
- Upgrade Jest to version 24.8.0

## 0.4.14 (May 7, 2019)

### Fixes

- Add missing `disabled` property to buttons components ([#54](https://github.com/salesforce/lwc-jest/pull/54))
- Add missing `disabled` property to buttons components ([#54](https://github.com/salesforce/lwc-jest/pull/54))

### Chores

- Remove old mock generation logic, rename mocks --> stubs ([#53](https://github.com/salesforce/lwc-jest/pull/53))
- Remove old mock generation logic, rename mocks --> stubs ([#53](https://github.com/salesforce/lwc-jest/pull/53))

## 0.4.13 (May 2, 2019)

### Fixes

- Update significant number of `lightning` stubs based on new generation script ([#50](https://github.com/salesforce/lwc-jest/pull/50))
- Add `type` prop to `<lightning-tile>` stub ([#48](https://github.com/salesforce/lwc-jest/pull/48))
- Add `formatFractionDigits` prop to `<lightning-input>` stub ([#47](https://github.com/salesforce/lwc-jest/pull/47))
- Update significant number of `lightning` stubs based on new generation script ([#50](https://github.com/salesforce/lwc-jest/pull/50))
- Add `type` prop to `<lightning-tile>` stub ([#48](https://github.com/salesforce/lwc-jest/pull/48))
- Add `formatFractionDigits` prop to `<lightning-input>` stub ([#47](https://github.com/salesforce/lwc-jest/pull/47))

### Chores

- Upgrade LWC to version 0.34.8 ([#44](https://github.com/salesforce/lwc-jest/pull/44))
- Update README with additional troubleshooting info on deasync ([#43](https://github.com/salesforce/lwc-jest/pull/43) [#49](https://github.com/salesforce/lwc-jest/pull/49))
- Upgrade LWC to version 0.34.8 ([#44](https://github.com/salesforce/lwc-jest/pull/44))
- Update README with additional troubleshooting info on deasync ([#43](https://github.com/salesforce/lwc-jest/pull/43) [#49](https://github.com/salesforce/lwc-jest/pull/49))

## 0.4.12 (March 11, 2019)

### Fixes

- `lightning/platformResourceLoader` mock APIs to return a resolved Promise ([#38](https://github.com/salesforce/lwc-jest/pull/38))
- `lightning/platformResourceLoader` mock APIs to return a resolved Promise ([#38](https://github.com/salesforce/lwc-jest/pull/38))

### Chores

- Upgrade LWC to version 0.34.7
- Upgrade LWC to version 0.34.7

## 0.4.11 (March 8, 2019)

### Fixes

- Set `process.env.NODE_ENV` to 'test' if unset for non-debug mode ([#34](https://github.com/salesforce/lwc-jest/pull/34))
- Fix code coverage option and remove `testURL` config ([#32](https://github.com/salesforce/lwc-jest/pull/32))
- Fix custom namespace resolution logic ([#30](https://github.com/salesforce/lwc-jest/pull/30))
- Add missing functions to `<lightning-input>` mock ([#22](https://github.com/salesforce/lwc-jest/pull/22))
- Set `process.env.NODE_ENV` to 'test' if unset for non-debug mode ([#34](https://github.com/salesforce/lwc-jest/pull/34))
- Fix code coverage option and remove `testURL` config ([#32](https://github.com/salesforce/lwc-jest/pull/32))
- Fix custom namespace resolution logic ([#30](https://github.com/salesforce/lwc-jest/pull/30))
- Add missing functions to `<lightning-input>` mock ([#22](https://github.com/salesforce/lwc-jest/pull/22))
28 changes: 14 additions & 14 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,23 +35,23 @@ socioeconomic status, or other similar personal characteristics.
Examples of behavior that contributes to creating a positive environment
include:

- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy toward other community members
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
- Showing empathy toward other community members

Examples of unacceptable behavior by participants include:

- The use of sexualized language or imagery and unwelcome sexual attention or
advances
- Personal attacks, insulting/derogatory comments, or trolling
- Public or private harassment
- Publishing, or threatening to publish, others' private information—such as
a physical or electronic address—without explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting
- Advocating for or encouraging any of the above behaviors
- The use of sexualized language or imagery and unwelcome sexual attention or
advances
- Personal attacks, insulting/derogatory comments, or trolling
- Public or private harassment
- Publishing, or threatening to publish, others' private information—such as
a physical or electronic address—without explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting
- Advocating for or encouraging any of the above behaviors

## Our Responsibilities

Expand Down
16 changes: 8 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,9 +79,9 @@ See the [Jest documentation](http://facebook.github.io/jest/docs/en/cli.html) fo

Debug mode lets you easily debug your Jest tests.

- Put a `debugger;` into your code
- Open `chrome://inspect`
- Run `sfdx-lwc-jest` with the `--debug` flag.
- Put a `debugger;` into your code
- Open `chrome://inspect`
- Run `sfdx-lwc-jest` with the `--debug` flag.

Pass other parameters to Jest after the `--` flag. For example,

Expand All @@ -93,9 +93,9 @@ sfdx-lwc-jest --debug -- --no-cache

If you prefer to debug inside Visual Studio Code, follow these steps:

- From the Visual Studio Code dropdowns, select Debug > Add Configuration....
- If you're prompted for an Environment choose any value.
- Mac users, replace the contents of the generated `launch.json` with the following. (for Windows users see the [Jest website](https://jestjs.io/docs/en/troubleshooting#debugging-in-vs-code) for launch.json contents).
- From the Visual Studio Code dropdowns, select Debug > Add Configuration....
- If you're prompted for an Environment choose any value.
- Mac users, replace the contents of the generated `launch.json` with the following. (for Windows users see the [Jest website](https://jestjs.io/docs/en/troubleshooting#debugging-in-vs-code) for launch.json contents).

```json
{
Expand All @@ -118,8 +118,8 @@ If you prefer to debug inside Visual Studio Code, follow these steps:
}
```

- Add a `jest.config.js` file to the root of the Salesforce DX project as described [here](#overriding-jest-config). You must add this file to run Jest from Visual Studio Code.
- To run tests, press F5 or select Debug > Start Debugging.
- Add a `jest.config.js` file to the root of the Salesforce DX project as described [here](#overriding-jest-config). You must add this file to run Jest from Visual Studio Code.
- To run tests, press F5 or select Debug > Start Debugging.

## Watch Mode

Expand Down

0 comments on commit e0608e6

Please sign in to comment.