@automattic/i18n-check-webpack-plugin 1.1.5 → 1.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +5 -0
- package/README.md +1 -9
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,10 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [1.1.6] - 2024-02-07
|
|
9
|
+
### Changed
|
|
10
|
+
- At some point a change in the toolchain (babel? terser?) broke one of the possible fixes for expression movement. Update the docs to stop recommending that fix. [#35452]
|
|
11
|
+
|
|
8
12
|
## [1.1.5] - 2023-12-06
|
|
9
13
|
### Changed
|
|
10
14
|
- Updated package dependencies. [#34416]
|
|
@@ -194,6 +198,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
194
198
|
### Added
|
|
195
199
|
- Initial release.
|
|
196
200
|
|
|
201
|
+
[1.1.6]: https://github.com/Automattic/i18n-check-webpack-plugin/compare/v1.1.5...v1.1.6
|
|
197
202
|
[1.1.5]: https://github.com/Automattic/i18n-check-webpack-plugin/compare/v1.1.4...v1.1.5
|
|
198
203
|
[1.1.4]: https://github.com/Automattic/i18n-check-webpack-plugin/compare/v1.1.3...v1.1.4
|
|
199
204
|
[1.1.3]: https://github.com/Automattic/i18n-check-webpack-plugin/compare/v1.1.2...v1.1.3
|
package/README.md
CHANGED
|
@@ -78,19 +78,11 @@ const
|
|
|
78
78
|
/* translators: This is a good example. */
|
|
79
79
|
example = __( 'Example', 'domain' );
|
|
80
80
|
```
|
|
81
|
-
In some cases even the assignment may be dropped. In that case, you can attach the comment directly to the function call
|
|
81
|
+
In some cases even the assignment may be dropped. In that case, you can attach the comment directly to the function call:
|
|
82
82
|
```js
|
|
83
83
|
const example =
|
|
84
84
|
/* translators: This is a good example. */
|
|
85
85
|
__( 'Example', 'domain' );
|
|
86
|
-
|
|
87
|
-
const example2 = __(
|
|
88
|
-
/* translators: This is a good example. */
|
|
89
|
-
'Example',
|
|
90
|
-
'domain'
|
|
91
|
-
);
|
|
92
|
-
|
|
93
|
-
const example3 = __( /* translators: This won't work. The comment must be on a line after the `__(`. */ 'Example', 'domain' );
|
|
94
86
|
```
|
|
95
87
|
|
|
96
88
|
Similarly in jsx, a comment placed like this may wind up misplaced:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@automattic/i18n-check-webpack-plugin",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.6",
|
|
4
4
|
"description": "A Webpack plugin to check that WordPress i18n hasn't been mangled by Webpack optimizations.",
|
|
5
5
|
"homepage": "https://github.com/Automattic/jetpack/tree/HEAD/projects/js-packages/i18n-check-webpack-plugin/#readme",
|
|
6
6
|
"bugs": {
|