-
-
Notifications
You must be signed in to change notification settings - Fork 446
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
Auto-configure inAppIncludes in Spring Boot integration. #966
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
sentry-spring-boot-starter/src/main/java/io/sentry/spring/boot/InAppIncludesResolver.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
quick question: why No breaking changes
is not checked? it's not really a breaking change, right?
It alters the previous behavior so not really breaking but once users upgrade and they didnt set this propery manually before they will see a change. Does it qualify as breaking? |
I see, luckily if manually set and now automatically detected, would be still the same values, IMO it's not a breaking change but got your point, maybe let's just describe this in the release notes so we don't need to minor bump, but only patch bump, wdyt/ |
…/InAppIncludesResolver.java Co-authored-by: Manoel Aranda Neto <5731772+marandaneto@users.noreply.github.com>
yeah 3.1.0 is also good enough, wouldn't break a build but worth noting a relevant change |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
📢 Type of change
📜 Description
Auto-configure
inAppIncludes
in Spring Boot integration by getting a package name from@SpringBootApplication
or@SpringBootConfiguration
annotated classes.💡 Motivation and Context
Less configuration and better experience for our users.
💚 How did you test it?
📝 Checklist