I’ve copied the Grid Component Example into a single-file component (Grid.vue). Within that component, I’m not able to access the columns prop. console.log(this.columns) always prints: [__ob__: Observer] to the log. Can someone tell me why? This works fine in their example on the page and in JSFiddle. Here’s my Grid.vue file: I’m using this component within another component like so:
Tag: vue-component
Access $refs from other components not in the same level as current component
I’m working on a Vue application. It has a header and then the main content. Nesting and structure as below I need to access an element in TheLogin.vue from OrderSummary.vue gives me an error “Cannot read property ‘$emit’ of undefined” so obviously I am not able to access $refs from other components. The question is how do I get hold
how to see changes in new data generated in a vue component?
Well I hope to explain, I’m generating this data from a component, when I click the checkbox changes in the generated data are not reflected, but when clicking the button with a data already in the instance changes are made, I appreciate if you explain Why or do they have a solution? this my code js html this live code
Open a Vuetify dialog from a component template in VueJS
I’m using the VueJS Vuetify framework and I need to open a dialog – that gets imported as a component template – from another template. Once the Menu button in App.vue got clicked, the Modal should open. Here is my setup: App.vue = navigation template with Menu button Modal.vue = Modal template, imported as global in main.js main.js Modal.vue Template:
Unable to import/export vuejs components
I have a folder like this. Classic and Modern are simple components with template, export default {} and a style. I am calling both inside index.js as: So, when I import this module as: I get this error Unknown custom element: – did you register the component correctly? For recursive components, make sure to provide the “name” option. I have
Vue – adding a Class-Name to a Component using a prop
I would like to make a custom component in Vue with the following props: text = text to be displayed in the link. icon = identifier of the icon to be displayed next to the link. < sidebar-link text=”Home” icon=”fa-home”> I have the following .Vue template for my component. Essentially I have the default Font-Awesome code in my template: and
How to set data into nuxt.js nuxt-link?
I’m trying to pass data into nuxt-link but nuxt-link is just returning a 404 error when I click on the link. It doesn’t seem to be getting and loading the file…. The second 2 links that use :href and hardcoding works Answer Nuxt uses vue-router by reading off the vue-router documentation you’ll be able to achieve what you want. router-link
Check if props in vue.js component template exists
After tried many variations, I don’t know how to properly style a component’s slot or partial code within <template></template> section. Is there a way to check if props <counter :recent=”true”></counter> from parent level exists, so in a Counter.vue in section <template></template> i would show a special html markup for it ? === UPDATED === Answer Here the default value for
Add errors to VeeValidate errors bag from parent component and listen from child components
I couldn’t find a guideline to implement this. How would you add data to errors bag from parent component and listen to the particular error from child components to show something conditionally? I’ve added the error to the errors bag from the parent component like the following: Now, from the child component, I’d like to show something conditionally depending on
Watching parent with prop doesn’t update during for loop
I have 2 components – <my-component> and <grand-child-comp>. In my root there is a multidimensional object and my component watches it with prop. In Vue debugger, I can see that my-component is getting and watching accountTypes object successfully. However, when trying to use it in my-component’s template, it doesn’t work. Lastly, accountTypes object looks like: Answer The problem is you’re