Unknown custom element errors about vuetify-form-base HOT 6 CLOSED

See #2, the last comment explain how to fix this kind of issue, just replace "{ VLayout, VCheckbox, VSelect }" by the components you need.

from vuetify-form-base.

Installations instructions unclear. How do I know what components I need? I am not calling them, vuetify-form-base is calling them and needs them.

If there are dependencies that vuetify-form-base needs it would be better if your component would require them itself.

from vuetify-form-base.

I am not the author of this component, just trying to help you :)
I do agree but i think it has just been made without a-la-carte in mind.
Also, if you would call v-row anywhere else in your code, it will be loaded and you won't require an extra step.

from vuetify-form-base.

Thanks @webdo for your explanation and suggestions.

vuetify-form-base uses intern dynamic components with <component :is="my-component"> This dynamic components must be registered locally as described in Dynamic Components.

Installations instructions and vuetify-form-base can not know which vuetify-components your application needs, because everyone declares the schema individually and according to his needs

One solution could be to do it without a-la-carte or take a look at mapping of components for local registration

Components Mapping :
A) First look for global registered components (custom components)
{ type:'mycustom', ...} map to component 'mycustom'
this works since 0.2.4

B) Look if Schema-Type exists in typeToComponent in vFormBase.vue
{ type:'text', ...} map to component mycustom 'v-text-field'

typeToComponent = {
    text: 'v-text-field',
    password: 'v-text-field',
    email: 'v-text-field',
    tel: 'v-text-field',
    url: 'v-text-field',
    search: 'v-text-field',
    number: 'v-text-field', 
    date: 'v-date-picker',   
    time: 'v-time-picker',
    color: 'v-color-picker',
    img: 'v-img',
    textarea: 'v-textarea',
    range: 'v-slider',
    file: 'v-file-input',
    switch: 'v-switch',
    checkbox: 'v-checkbox',
    
 }

C) Finally try to prepend schema-type with 'v-' in order to get a valid vuetify component
{ type:'slider', ...} map to component mycustom 'v-slider'

from vuetify-form-base.

The issue here is that with Vuetify 2.3.10, some component names were changed, for example v-content is now named v-main, this is a vuetify issue. If for example, this library has a hard coded v-content "internally", it should now be named "v-main". This also means that the documentation for this library where v-content was used, should now be updated to reflect v-main, provided that the vuetify version used by this lib is 2.3.10

I hope this brings in some clarity.

Ta!

from vuetify-form-base.

Hi and THX for your contribution.

v-content is not hardcoded in vuetify-form-base. But I will update the documentation next time

from vuetify-form-base.