Skip to content
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

fix: fix module options #59

Merged
merged 4 commits into from
Apr 2, 2019
Merged

fix: fix module options #59

merged 4 commits into from
Apr 2, 2019

Conversation

rchl
Copy link
Member

@rchl rchl commented Feb 25, 2019

With no top level 'sentry' object defined in nuxt-config.js, the code
would try to access property of undefined object as
this.options.sentry is undefined. Fixed by using deepmerge package which
both fixes the problem and makes code cleaner.

Also fixed problem with merging dsn property value with the object.
As dsn value is a string, don't use ... on it as that would turn string
into an array of letters.

With no top level 'sentry' object defined in nuxt-config.js, the code
would try to access property of undefined object as
this.options.sentry is undefined. Fixed by using deepmerge package which
both fixes the problem and makes code cleaner.

Also fixed problem with merging dsn property value with the object.
As dsn value is a string, don't use ... on it as that would turn string
into an array of letters.
@rchl rchl mentioned this pull request Feb 25, 2019
rchl added 2 commits April 2, 2019 15:39
Sentry options object is called "config", not "options"
@pi0
Copy link
Member

pi0 commented Apr 2, 2019

Thanks @rchl for this fix and sorry for long delay.

@pi0 pi0 changed the title Fix problems with loading module options fix: fix module options Apr 2, 2019
@pi0 pi0 merged commit 9b4d723 into nuxt-community:master Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants