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

Remove implicit Sentry initialization #62

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andyrichardson
Copy link

Thanks for the project!

This is the best I could do without introducing a breaking change. I'd recommend removing Sentry initialization altogether in a future major release.

I haven't tested this

Fix #57 and #56

@glensc
Copy link
Collaborator

glensc commented Mar 26, 2023

one change per commit please. and describe the change in commit message. also, describe the supposed new usage in readme. totally different changes should go to different pr.

@mwillbanks
Copy link

@glensc correct me if i am wrong, but this is only targeting a single change but closes multiple issues. i'm more than willing to rebuild this PR to incorporate the change here and update the readme, tests, etc.

@glensc
Copy link
Collaborator

glensc commented Apr 25, 2023

changing dependency to peer dependency can definitely be a separate commit and a PR. the other changes are also questionable and are already breaking. see the GitHub actions output.

@andyrichardson
Copy link
Author

Hey hey! I did this blind but I can spend some time to fix the Typescript issues if you want 👍

Just looking to help out - any mutual efforts to collaborate are appreciated!

@glensc
Copy link
Collaborator

glensc commented Apr 29, 2023

seems you want this merged. I can help with merge if I understand the changes and they don't break things. those were my requirements. the current state is not acceptable for me to put my name on the merge.

@glensc glensc marked this pull request as draft February 12, 2024 20:13
@glensc
Copy link
Collaborator

glensc commented Feb 12, 2024

marking as draft. this is nowhere near complete. any of the errors that ci has reported have not been fixed. and as original author has written, they have not tested this.

this might have moved faster if separate changes were put to different pull requests.

public constructor(options?: any, initializeSentry?: boolean = true) {
const validatedOptions = this.validateOptions(options || {});

if (initializeSentry) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about having this set via options? also the what would get sentry return below?

the only way oi see this to work, if you pass an instance of Sentry to the constructor. and use that value in rest of the code.

@glensc
Copy link
Collaborator

glensc commented Feb 12, 2024

I put something like this quickly together from my notes above:

@glensc
Copy link
Collaborator

glensc commented Aug 27, 2024

Extracted peerDependency change to separate PR

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.

Sentry should not be a dependency but rather a peer dependency
3 participants