The computed property "accessToken" is already defined as a prop.

[Patrick Heneise]

I'm using accessToken as a computed property across my app for authentication. I'm not sure if there is a way to scope accessToken to the Mapbox component?

[Nick Ford]

I'm not the maintainer but are you adding that as a mixin? You could check to see if the name of the component is 'mapbox' before adding the computed.

[Patrick Heneise]

That's an interesting take, I'll give that a try, thanks!

[Pete Hegman]

Hmm not totally sure why this would be an issue, accessToken prop should only be defined internally inside this component and shouldn't have any affect on the rest of the application. If you can post how you are using this component that would be helpful, for now I am closing.

[Nick Ford]

@phegmen i think they were using a global mixin to all that property to all components

[Pete Hegman]

Ahh okay that makes sense. I don’t have very much experience with Global Mixins, but it looks like you should be able to customize the merging of props. Here is the documentation: https://vuejs.org/v2/guide/mixins.html#Custom-Option-Merge-Strategies https://vuejs.org/v2/api/#optionMergeStrategies It looks like the third param of optionMergeStrategies is the Vue instance so you may be able to detect what component is being merged and exclude it. I have not played around with this at all but this is the route I would explore.

…

On Feb 14, 2019, at 6:25 AM, Nick Ford ***@***.***> wrote: @phegmen i think they were using a global mixin to all that property to all components — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

[Patrick Heneise]

I'll have a look, thanks!