profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/posva/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Eduardo San Martin Morote posva Freelance Paris https://esm.dev Member of the @vuejs core team Speaker, trainer. From 🇪🇸, lives in 🇫🇷

posva/catimg 923

🦦 Insanely fast image printing in your terminal

Gozala/selfish 160

Class-free, pure prototypal inheritance

brillout/awesome-vue-refactor 31

A curated list of awesome things related to Vue.js

ArthurSonzogni/CppBot 17

Portable C++ tools for bot creations : keyboard and mouse event generations, screen capture !

posva/clipboard-text 11

Simple and small copy-text-to-the-clipboard-utility with IE11 support

posva/2d-collisions 2

Collision for 2D using the SAT theorem with Rectangles

posva/babel 2

🐠 Babel is a compiler for writing next generation JavaScript.

issue commentvuejs/vue-router-next

Dynamically added child with an empty path isn't being rendered

You also need to renavigate after adding routes like shown in docs

Namysh

comment created time in 16 hours

issue closedvuejs/vue

Custom Validator is running after Computed Property

Version

2.6.14

Reproduction link

github.com

Steps to reproduce

1 - yarn install 2 - yarn serve 3 - Add a breakpoint inside the Options Validator 4 - Add a breakpoint inside the availableOptions computed property 5 - Refresh the page and verify that the availableOptions computed property was reached before the Validator function

What is expected?

the validator function should run before the computed property

What is actually happening?

the validator function runs after the computed property


Related https://github.com/vuejs/vue/issues/12286

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 18 hours

AllanOricil

issue commentvuejs/vue

Custom Validator is running after Computed Property

Please provide a boiled down repro like asked in the issue helper

AllanOricil

comment created time in 18 hours

push eventposva/vue-use-spring

renovate[bot]

commit sha 46ca8b2ce635b26b224c9c84730b2b49e1b7e886

chore(deps): update dependency @types/jest to v27 (#195)

view details

push time in 18 hours

PR merged posva/vue-use-spring

chore(deps): update dependency @types/jest to v27

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/jest ^26.0.24 -> ^27.0.1 age adoption passing confidence

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+9 -57

1 comment

2 changed files

renovate[bot]

pr closed time in 18 hours

push eventposva/renovate-config

renovate[bot]

commit sha 28825e5f5ddad517e01087ea1ef5756218380704

chore(deps): update dependency renovate to v27 (#27)

view details

push time in 18 hours

PR merged posva/renovate-config

chore(deps): update dependency renovate to v27

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
renovate (source) ^26.21.7 -> ^27.14.1 age adoption passing confidence

Release Notes

<details> <summary>renovatebot/renovate</summary>

v27.14.1

Compare Source

27.14.1 (2021-09-20)
Bug Fixes
Tests
Documentation
Miscellaneous Chores

v27.14.0

Compare Source

Features

v27.13.0

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v27.12.2

Compare Source

27.12.2 (2021-09-17)
Build System

v27.12.1

Compare Source

27.12.1 (2021-09-17)
Build System

v27.12.0

Compare Source

Features
Documentation

v27.11.2

Compare Source

27.11.2 (2021-09-17)
Bug Fixes
Miscellaneous Chores
  • deps: update dependency conventional-changelog-conventionalcommits to v4.6.1 (#​11785) (e6d0edb)
  • deps: update dependency type-fest to v2.3.1 (#​11788) (300b8b6)

v27.11.1

Compare Source

27.11.1 (2021-09-16)
Bug Fixes
Miscellaneous Chores

v27.11.0

Compare Source

Features

v27.10.0

Compare Source

Features

v27.9.1

Compare Source

27.9.1 (2021-09-16)
Bug Fixes
Tests

v27.9.0

Compare Source

Features
Miscellaneous Chores
Continuous Integration

v27.8.2

Compare Source

27.8.2 (2021-09-15)
Bug Fixes
Miscellaneous Chores
Tests

v27.8.1

Compare Source

27.8.1 (2021-09-15)
Build System

v27.8.0

Compare Source

Features
  • manager/terraform: support range strategy update lockfile (#​11720) (12ae0d1)

v27.7.1

Compare Source

27.7.1 (2021-09-15)
Bug Fixes

v27.7.0

Compare Source

Features
  • manager/nuget: update msbuild-sdks section in global.json (#​11707) (196df0d)

v27.6.5

Compare Source

27.6.5 (2021-09-14)
Bug Fixes
  • manager/gitlabci: name is not directly followed by image tag (#​11647) (03ac68e)
Documentation
Tests

v27.6.4

Compare Source

27.6.4 (2021-09-14)
Bug Fixes
Miscellaneous Chores

v27.6.3

Compare Source

27.6.3 (2021-09-14)
Bug Fixes
Miscellaneous Chores

v27.6.2

Compare Source

27.6.2 (2021-09-13)
Build System

v27.6.1

Compare Source

27.6.1 (2021-09-13)
Bug Fixes

v27.6.0

Compare Source

Features
  • manager/terraform/lockfile: support multiple deps during dep update (#​11630) (f937f73)
Documentation
Miscellaneous Chores

v27.5.0

Compare Source

Features
Documentation

v27.4.2

Compare Source

27.4.2 (2021-09-12)
Bug Fixes
Tests

v27.4.1

Compare Source

27.4.1 (2021-09-11)
Documentation
Tests
Build System

v27.4.0

Compare Source

Features
Bug Fixes
Tests

v27.3.3

Compare Source

27.3.3 (2021-09-10)
Bug Fixes
Continuous Integration

v27.3.2

Compare Source

27.3.2 (2021-09-09)
Bug Fixes

v27.3.1

Compare Source

27.3.1 (2021-09-09)
Bug Fixes
Miscellaneous Chores
Tests
Documentation
  • Document update behavior for gems without version constraints (#​11644) (0ee8440)
  • update table Major platform features not supported by Renovate (#​11649) (6eafd2f)

v27.3.0

Compare Source

Features

v27.2.0

Compare Source

Features

v27.1.0

Compare Source

Features

v27.0.0

Compare Source

⚠ BREAKING CHANGES
  • pre-commit manager is no longer enabled by default, and must be opted into manually.
  • Git >=2.33.0 is now required
Features

</details>


Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+60 -32

0 comment

2 changed files

renovate[bot]

pr closed time in 18 hours

issue closedvuejs/vue

in Vue template, space and new line between element tags are not ignored

Version

2.6.14

Reproduction link

sfc.vuejs.org/

Steps to reproduce

<template>
	<div>
		<p>
			hello world
		</p>
	</div>
</template>

Inspect "hello world". There are spaces before and after "hello world" cause by spacing and newline in the template.

What is expected?

<p>hello world</p>

What is actually happening?

<p> hello world </p>


The space before and after "hello world" is not wanted.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 18 hours

jdchen2021

issue commentvuejs/vue

in Vue template, space and new line between element tags are not ignored

This is expected behavior and consistent with how HTML works

It can be configured with the compiler options for whitespace and it is documented

jdchen2021

comment created time in 18 hours

issue commentvuejs/vue-router-next

Dynamically added child with an empty path isn't being rendered

All root paths must start with a leading slash. There should be a warning about it in the console

Namysh

comment created time in 18 hours

issue closedvuejs/vue

[typescript] Properties with `default` value should not have "... | undefined" type

What problem does this feature solve?

When using TypeScript, any prop that has a default value is still inferred as <Type> | undefined.

For example:

  1. Create a component
  2. Add a property with type: Number and default: 5, while not required: true

Expected: the prop type to be number Actual: the prop type is number | undefined

<script lang="ts">
import Vue from 'vue';

export default Vue.extend({
  props: {
    testProp: {
      type: Number,
      default: 5,
    },
  },
  mounted() {
    this.testProp; // testProp: number | undefined
  },
});
</script>

This is reproducible in

  • vue 2.6.14
  • vue 3.2.12
  • @vue/composition-api 1.1.5

What does the proposed API look like?

The types should account for a defined default, the way they account for required: true.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 18 hours

larvanitis

issue commentvuejs/vue

[typescript] Properties with `default` value should not have "... | undefined" type

Open a new issue with an actual repro for Vue 3 or for Vue 2 in the Vue repo instead

larvanitis

comment created time in 18 hours

issue commentvuejs/vue

Provide Vue version in default export

Using Vue Demi is really the recommended approach 🙂 Its size is empty at the end!

AustinGil

comment created time in a day

issue closedvuejs/vue

Custom Validator for props should always run Before Computed properties

What problem does this feature solve?

Vue 2.6.14

Computed Properties are called before Props Custom Validators. I think It does not make sense, because If I declare a validator for my prop and it returns false, I think that Component shouldn't even be rendered. I also think it shouldn't even waste computing time/resources calculating a computed prop dependant on a prop that its validator returned false. But Vue wastes time because the Validator is called after the computed prop method, meaning that the Computed Property does not know yet that the Validator returned false. Is there a reason for that?

What does the proposed API look like?

Custom Validator for Props should always run before Computed properties, when that computed property is dependant on the Prop that has a Custom Validator that returns false. This way if the Prop validator returned false, Vue won't waste computing time/resources to calculate the Computed Property.

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 2 days

AllanOricil

issue commentvuejs/vue

Custom Validator for props should always run Before Computed properties

This is probably expected depending on how you pass the prop. Most of the time validators will run before computed, but at the end it shouldn't matter. If you think this is a bug, open a new issue with a repro to provide more context

AllanOricil

comment created time in 2 days

issue closedvuejs/vue

Provide Vue version in default export

What problem does this feature solve?

As a library author, it's hard to know what version of Vue is running on both v2 and v3.

Vue 2 provides the following:

import Vue from 'vue'
console.log(Vue.version)

Vue 3 offers

import { version } from 'vue'
console.log(version)

But it's hard to use a system that works for both. Version 3 does not have a default export, so trying to use Vue leads to warnings or ""export 'default' (imported as 'Vue') was not found in 'vue'"

A similar warning happens with trying to get version from named exports in a version 2 project.

My proposed solution would be to add a default export to Vue 3 that provides some context.

What does the proposed API look like?

From the main Vue.js entrypoint

export default {
  version: {vue version imported from package.json}
}

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 2 days

AustinGil

issue commentvuejs/vue

Provide Vue version in default export

This makes more sense in Vue Demi Vue 3 simply doesn't have a default export, it would be misleading to have one for migrating apps

AustinGil

comment created time in 2 days

issue commentvuejs/vue-router-next

Route not matched properly after browser refresh

This is because you are using end: false, so it matches the one with the custom regexp. Remove that option, you most likely don't need it. It's there for dynamic routing but some rankings are still incompatible.

Metalmi

comment created time in 2 days

issue closedvuejs/vue-router

路由history和scrollBehavior()函数的冲突

Version

3.5.2

Reproduction link

codesandbox.io

Steps to reproduce

const router = new VueRouter({ routes , mode:'history', scrollBehavior() { return {x:0,y:0} } })

What is expected?

在浏览器输入localhost:8080////// 可以正常访问

What is actually happening?

显示空白页,控制台报错: Failed to execute 'replaceState' on 'History': A history state object with URL 'http:' cannot be created in a document with origin 'http://localhost:8081' and URL 'http://localhost:8081///////'."


困扰了我三天的一个问题,希望可以得到解决。是我的使用方式有问题,还是确实是个bug呢?

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 2 days

SILENCEXZL

issue commentvuejs/vue-router

路由history和scrollBehavior()函数的冲突

Duplicate of #2593

SILENCEXZL

comment created time in 2 days

PR closed vuejs/vue

Update README.md

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one)

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

  • [ ] Yes
  • [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [ ] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
  • [ ] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
  • [ ] New/updated tests are included

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+1 -0

0 comment

1 changed file

saja-aish12

pr closed time in 3 days

issue closedvuejs/vue

Add shorthand for default prop value

What problem does this feature solve?

Easier syntax for setting the most common attribute (why a shorthand for setting the type and not for setting the default value?)

What does the proposed API look like?

props {
  title: this.title || this.blok.title || "vue",
}

Replacing :

props {
  title: {
    default: (value) => {
    value || this.blok.title || "menu"
  },
},

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 3 days

Rednas83

issue commentvuejs/vue

Add shorthand for default prop value

This isn't possible. The this keyword doesn't work like that

Rednas83

comment created time in 3 days

issue closedvuejs/vue-next

el.attributes.length is wrong in directive.(自定义指令中,el.attributes.length 与实际不符,el.attributes.length 总为0)

Version

3.2.12

Reproduction link

codepen.io

Steps to reproduce

// v-directive app.directive('test', { created(el, binding) { console.log('attributes.length:', el.attributes.length) // 0 } }) // test.vue <div v-test attr1 attr2>something<div/>

What is expected?

console.log(el.attributes.length) // 2

What is actually happening?

console.log(el.attributes.length) // 0

<!-- generated by vue-issues. DO NOT REMOVE -->

closed time in 3 days

hantaogo

PR closed vuejs/vue

added vue

<!-- Please make sure to read the Pull Request Guidelines: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

What kind of change does this PR introduce? (check at least one)

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [ ] Build-related changes
  • [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

  • [ ] Yes
  • [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • [ ] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
  • [ ] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
  • [ ] New/updated tests are included

If adding a new feature, the PR's description includes:

  • [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

+107376 -78679

0 comment

394 changed files

shafirasya

pr closed time in 3 days

push eventposva/pinia

Filip Sobol

commit sha 041db3e9739daee8f4c7ca3e7f4e439ede919cb8

Update code example in docs (#683)

view details

push time in 4 days

PR merged posva/pinia

Update code example in docs
+1 -1

0 comment

1 changed file

filipsobol

pr closed time in 4 days

PullRequestReviewEvent