Bug: autocomplete component: The computed property "fields" is already defined as a prop.

[websitevirtuoso]

Describe the bug
A clear and concise description of what the bug is.
I am trying to migrate from old vue-gmap plugin to your lib. Got this error
My application using vuetify. Somewhere creating a computed property with the name "fields".
I don't know where but know that your plugin doing the same.
SO I got next error:

`
[Vue warn]: The computed property "fields" is already defined as a prop.

found in

---> at node_modules/gmap-vue/dist/components/autocomplete.vue

at src/views/property/Create.vue

at src/components/layout/Index.vue

at src/App.vue

`

Expected behaviour
Should work without error The computed property "fields" is already defined as a prop.

Current behaviour
Display error: The computed property "fields" is already defined as a prop.

Desktop:

• OS: Ubuntu 19.04
• Browser chrome
• Version 86.0.4240.198

Versions

• Node: 12
• NPM: 6.14.9

Package manager

• NPM

Plugin version

• 1.5.0

[close-issue-app]

This issue is closed because it does not meet our issue template. Please read it.

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[websitevirtuoso]

@diegoazh

[diegoazh]

@websitevirtuoso can you rewrite this issue but please you don't need to paste your package.json in the issue template because the boot will close your issue, because it doesn't follow our issue template if you want to paste it please leave it in a comment after creating the issue.
Another option is to fix this issue and leave a comment here and after that, I can reopen this issue and the bot will not close it anymore.

[websitevirtuoso]

Package json

`
{
"name": "ecom-dashboard",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build && rm -rf ./dist/**/*.js.map",
"lint": "vue-cli-service lint",
"apollo": "vue-cli-service apollo:watch",
"apollo:run": "vue-cli-service apollo:run"
},
"dependencies": {
"@casl/ability": "^4.1.6",
"@casl/vue": "^1.1.1",
"@sentry/browser": "^5.27.4",
"@sentry/integrations": "^5.27.4",
"@sentry/webpack-plugin": "^1.13.0",
"core-js": "^3.7.0",
"cropperjs": "^1.5.9",
"gmap-vue": "^1.5.0",
"graphql-type-json": "^0.3.2",
"ramda": "^0.27.1",
"tiptap-vuetify": "^2.24.0",
"vee-validate": "^2.2.15",
"vue": "^2.6.12",
"vue-2-crumbs": "^0.5.4",
"vue-apollo": "^3.0.5",
"vue-moment": "^4.1.0",
"vue-router": "^3.4.9",
"vuedraggable": "^2.24.3",
"vuetify": "^2.3.18",
"vuex": "^3.5.1",
"vuex-i18n": "^1.13.1"
},
"devDependencies": {
"@babel/core": "^7.12.7",
"@babel/eslint-parser": "^7.12.1",
"@mdi/font": "^5.8.55",
"@vue/cli-plugin-babel": "^4.5.9",
"@vue/cli-plugin-eslint": "^4.5.9",
"@vue/cli-service": "^4.5.9",
"@vue/eslint-config-standard": "^5.1.2",
"eslint": "^7.14.0",
"eslint-plugin-graphql": "^4.0.0",
"eslint-plugin-import": "^2.22.1",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-standard": "^4.1.0",
"eslint-plugin-vue": "^7.1.0",
"graphql-tag": "^2.11.0",
"sass": "^1.29.0",
"sass-loader": "^10.1.0",
"vue-cli-plugin-apollo": "^0.21.3",
"vue-cli-plugin-vuetify": "^2.0.7",
"vue-template-compiler": "^2.6.12",
"vuetify-loader": "^1.6.0",
"webpack-bundle-analyzer": "^4.1.0"
},
"engines": {
"node": ">= 10.0.0",
"npm": ">= 6.8.0"
}
}

`

[websitevirtuoso]

@diegoazh Thanks for help. I changed message to your template/ Let me know if it works

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[julienperrault]

I've the same problem.

I'm using pug, so that's is my component (with no customs props).

<template lang="pug">
    gmap-autocomplete
</template>

[websitevirtuoso]

@julienperrault I had to fork and fix it. Almost all issues bot closing. very sad

[diegoazh]

@julienperrault sorry about that, the bot causes many problems, test the new version 2.0.0 and check the new documentation page to, please let me know if the issue persists @websitevirtuoso all components are working well in the documentation.

[create-issue-branch]

Branch issue-118-Bug_autocomplete_component_The_computed_property_fields_is_already_defined_as_a_prop created!

[diegoazh]

@julienperrault about the bot, please try to open a new issue for test and check if the bot works correctly now, I do that and works well for me but I'm not completely sure if it is fixed or not.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[diegoazh]

@websitevirtuoso @julienperrault can you test the last v2.0.3 and let me know if the bug persists.

[razukc]

@websitevirtuoso @julienperrault can you test the last v2.0.3 and let me know if the bug persists.

I've tested it. The issue still exists.

[diegoazh]

Can you share with me you component @razukc? to reproduce the issue locally, thanks.

[diegoazh]

I think is fixed on v2.0.4 can you confirm that @razukc?

[razukc]

I think is fixed on v2.0.4 can you confirm that @razukc?

I tested it and I confirm that it is working. But for some reason, yarn add gmap-vue is installing gmap-vue@3.0.0. However, the warning is gone now. @diegoazh

[diegoazh]

Excellent @razukc I'll mark this issue as solved. The v3.0.0 is the last one that I land a few days ago and more changes are coming.

[dhcmega]

Hi, I'm on 2.0.4 with "@googlemaps/markerclusterer": "^1.0.26", and I'm getting this same error: TypeError: this.$clusterObject.repaint

Is this only fix on v3 or also for v2?
thanks

[diegoazh]

Hi, that bug was fixed on version 3.

[dhcmega]

I don't know why I thought v3 was for vue v3. It worked right away. Thanks!