Skip to content

Specifying one single value for the props property with named views #1779

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
green-coder opened this issue Oct 3, 2017 · 0 comments
Open
Labels
contribution welcome feature request fixed on 4.x This issue has been already fixed on the v4 but exists in v3 improvement

Comments

@green-coder
Copy link

What problem does this feature solve?

When passing from a component to multiple (named) ones, we also need to change the way the props property is defined. If the user of the lib is not aware of that change, the props are not passed to his components anymore and his program stops to work normally.

This code break can be avoided if we interpret the single-component prop config as valid for multiple-components by extension.

What does the proposed API look like?

  components: {
    default: MyComponent,
    sideBar: MySideBar
  },
  props: {
    default: true,
    sideBar: true
  },

could be written as:

  components: {
    default: MyComponent,
    sideBar: MySideBar
  },
  props: true,

The same for the function-based version of props.

@posva posva changed the title Compatible way of passing props to named views Specifying one single value for the props property with named views Oct 3, 2017
@posva posva added contribution welcome fixed on 4.x This issue has been already fixed on the v4 but exists in v3 and removed contribution welcome labels May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution welcome feature request fixed on 4.x This issue has been already fixed on the v4 but exists in v3 improvement
Projects
None yet
Development

No branches or pull requests

2 participants