Skip to content

Commit 3a3bd84

Browse files
committed
fix: format
1 parent 9267484 commit 3a3bd84

File tree

8 files changed

+3
-20
lines changed

8 files changed

+3
-20
lines changed

.github/contributing.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -38,20 +38,17 @@ Hi! I'm really excited that you are interested in contributing to Vue.js. Before
3838
### Pull Request Checklist
3939

4040
- Vue core has two primary work branches: `main` and `minor`.
41-
4241
- If your pull request is a feature that adds new API surface, it should be submitted against the `minor` branch.
4342

4443
- Otherwise, it should be submitted against the `main` branch.
4544

4645
- [Make sure to tick the "Allow edits from maintainers" box](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork). This allows us to directly make minor edits / refactors and saves a lot of time.
4746

4847
- If adding a new feature:
49-
5048
- Add accompanying test case.
5149
- Provide a convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
5250

5351
- If fixing a bug:
54-
5552
- If you are resolving a special issue, add `(fix #xxxx[,#xxxx])` (#xxxx is the issue id) in your PR title for a better release log, e.g. `update entities encoding/decoding (fix #3899)`.
5653
- Provide a detailed description of the bug in the PR. Live demo preferred.
5754
- Add appropriate test coverage if applicable. You can check the coverage of your code addition by running `nr test-coverage`.
@@ -69,9 +66,7 @@ Hi! I'm really excited that you are interested in contributing to Vue.js. Before
6966
- The PR should fix the intended bug **only** and not introduce unrelated changes. This includes unnecessary refactors - a PR should focus on the fix and not code style, this makes it easier to trace changes in the future.
7067

7168
- Consider the performance / size impact of the changes, and whether the bug being fixes justifies the cost. If the bug being fixed is a very niche edge case, we should try to minimize the size / perf cost to make it worthwhile.
72-
7369
- Is the code perf-sensitive (e.g. in "hot paths" like component updates or the vdom patch function?)
74-
7570
- If the branch is dev-only, performance is less of a concern.
7671

7772
- Check how much extra bundle size the change introduces.
@@ -265,7 +260,6 @@ This repository employs a [monorepo](https://en.wikipedia.org/wiki/Monorepo) set
265260
- `vue`: The public facing "full build" which includes both the runtime AND the compiler.
266261

267262
- Private utility packages:
268-
269263
- `dts-test`: Contains type-only tests against generated dts files.
270264

271265
- `sfc-playground`: The playground continuously deployed at https://play.vuejs.org. To run the playground locally, use [`nr dev-sfc`](#nr-dev-sfc).

.github/maintenance.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,15 +48,13 @@ Depending on the type of the PR, different considerations need to be taken into
4848
- Performance: if a refactor PR claims to improve performance, there should be benchmarks showcasing said performance unless the improvement is self-explanatory.
4949

5050
- Code quality / stylistic PRs: we should be conservative on merging this type PRs because (1) they can be subjective in many cases, and (2) they often come with large git diffs, causing merge conflicts with other pending PRs, and leading to unwanted noise when tracing changes through git history. Use your best judgement on this type of PRs on whether they are worth it.
51-
5251
- For PRs in this category that are approved, do not merge immediately. Group them before releasing a new minor, after all feature-oriented PRs are merged.
5352

5453
### Reviewing a Feature
5554

5655
- Feature PRs should always have clear context and explanation on why the feature should be added, ideally in the form of an RFC. If the PR doesn't explain what real-world problem it is solving, ask the contributor to clarify.
5756

5857
- Decide if the feature should require an RFC process. The line isn't always clear, but a rough criteria is whether it is augmenting an existing API vs. adding a new API. Some examples:
59-
6058
- Adding a new built-in component or directive is "significant" and definitely requires an RFC.
6159
- Template syntax additions like adding a new `v-on` modifier or a new `v-bind` syntax sugar are "substantial". It would be nice to have an RFC for it, but a detailed explanation on the use case and reasoning behind the design directly in the PR itself can be acceptable.
6260
- Small, low-impact additions like exposing a new utility type or adding a new app config option can be self-explanatory, but should still provide enough context in the PR.
@@ -70,7 +68,6 @@ Depending on the type of the PR, different considerations need to be taken into
7068
- Implementation: code style should be consistent with the rest of the codebase, follow common best practices. Prefer code that is boring but easy to understand over "clever" code.
7169

7270
- Size: bundle size matters. We have a GitHub action that compares the size change for every PR. We should always aim to realize the desired changes with the smallest amount of code size increase.
73-
7471
- Sometimes we need to compare the size increase vs. perceived benefits to decide whether a change is justifiable. Also take extra care to make sure added code can be tree-shaken if not needed.
7572

7673
- Make sure to put dev-only code in `__DEV__` branches so they are tree-shakable.
@@ -80,7 +77,6 @@ Depending on the type of the PR, different considerations need to be taken into
8077
- Make sure it doesn't accidentally cause dev-only or compiler-only code branches to be included in the runtime build. Notable case is that some functions in @vue/shared are compiler-only and should not be used in runtime code, e.g. `isHTMLTag` and `isSVGTag`.
8178

8279
- Performance
83-
8480
- Be careful about code changes in "hot paths", in particular the Virtual DOM renderer (`runtime-core/src/renderer.ts`) and component instantiation code.
8581

8682
- Potential Breakage

packages/compiler-sfc/README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ This package contains lower level utilities that you can use if you are writing
1111
The API is intentionally low-level due to the various considerations when integrating Vue SFCs in a build system:
1212

1313
- Separate hot-module replacement (HMR) for script, template and styles
14-
1514
- template updates should not reset component state
1615
- style updates should be performed without component re-render
1716

packages/runtime-core/__tests__/rendererAttrsFallthrough.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -573,7 +573,7 @@ describe('attribute fallthrough', () => {
573573
const Child = {
574574
props: [],
575575
render() {
576-
return openBlock(), createBlock('div')
576+
return (openBlock(), createBlock('div'))
577577
},
578578
}
579579

packages/runtime-core/__tests__/rendererFragment.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -416,7 +416,7 @@ describe('renderer: fragment', () => {
416416
const root = nodeOps.createElement('div')
417417

418418
const renderFn = () => {
419-
return openBlock(true), createBlock(Fragment, null)
419+
return (openBlock(true), createBlock(Fragment, null))
420420
}
421421

422422
render(renderFn(), root)

packages/runtime-core/src/compat/componentAsync.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ export function convertLegacyAsyncComponent(
3535
let resolve: (res: LegacyAsyncReturnValue) => void
3636
let reject: (reason?: any) => void
3737
const fallbackPromise = new Promise<Component>((r, rj) => {
38-
;(resolve = r), (reject = rj)
38+
;((resolve = r), (reject = rj))
3939
})
4040

4141
const res = comp(resolve!, reject!)

packages/vue-compat/README.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,6 @@ The following workflow walks through the steps of migrating an actual Vue 2 app
4141
### Installation
4242

4343
1. Upgrade tooling if applicable.
44-
4544
- If using custom webpack setup: Upgrade `vue-loader` to `^16.0.0`.
4645
- If using `vue-cli`: upgrade to the latest `@vue/cli-service` with `vue upgrade`
4746
- (Alternative) migrate to [Vite](https://vitejs.dev/) + [vite-plugin-vue2](https://github.com/underfin/vite-plugin-vue2). [[Example commit](https://github.com/vuejs/vue-hackernews-2.0/commit/565b948919eb58f22a32afca7e321b490cb3b074)]
@@ -160,7 +159,6 @@ The following workflow walks through the steps of migrating an actual Vue 2 app
160159
5. After fixing the errors, the app should be able to run if it is not subject to the [limitations](#known-limitations) mentioned above.
161160

162161
You will likely see a LOT of warnings from both the command line and the browser console. Here are some general tips:
163-
164162
- You can filter for specific warnings in the browser console. It's a good idea to use the filter and focus on fixing one item at a time. You can also use negated filters like `-GLOBAL_MOUNT`.
165163

166164
- You can suppress specific deprecations via [compat configuration](#compat-configuration).

packages/vue/README.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@
55
### From CDN or without a Bundler
66

77
- **`vue(.runtime).global(.prod).js`**:
8-
98
- For direct use via `<script src="...">` in the browser. Exposes the `Vue` global.
109
- Note that global builds are not [UMD](https://github.com/umdjs/umd) builds. They are built as [IIFEs](https://developer.mozilla.org/en-US/docs/Glossary/IIFE) and is only meant for direct use via `<script src="...">`.
1110
- In-browser template compilation:
@@ -21,7 +20,6 @@
2120
### With a Bundler
2221

2322
- **`vue(.runtime).esm-bundler.js`**:
24-
2523
- For use with bundlers like `webpack`, `rollup` and `parcel`.
2624
- Leaves prod/dev branches with `process.env.NODE_ENV` guards (must be replaced by bundler)
2725
- Does not ship minified builds (to be done together with the rest of the code after bundling)
@@ -39,12 +37,10 @@
3937
`esm-bundler` builds of Vue expose global feature flags that can be overwritten at compile time:
4038

4139
- `__VUE_OPTIONS_API__`
42-
4340
- Default: `true`
4441
- Enable / disable Options API support
4542

4643
- `__VUE_PROD_DEVTOOLS__`
47-
4844
- Default: `false`
4945
- Enable / disable devtools support in production
5046

0 commit comments

Comments
 (0)