-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ref(core): Introduce protected _getBreadcrumbs()
on scope
#8961
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
Conversation
size-limit report 📦
|
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.
Since this is public API and removing it (even when in the process of doing a major) is usually a lot of pain (in regards to documentation - migration guides etc), would you care to elaborate why we need this?
yeah, sure, sorry, could have def. elaborated more on this. For POTEL I want to (experimentally) overwrite this to have a different logic to get the breadcrumbs for a scope. I figured it would be the cleanest solution to expose this as a function (similar to others we already have like this on the scope, like |
Making it easier to potentially change this e.g. for POTEL.
e8ed426
to
a68bf32
Compare
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
If we do not like this being public API I could also make it a protected function, which should be good enough to be able to overwrite it in a subclass
No strong feeling but if it's not too much work then, let's do this. We can still make it public later on but reversing things is harder.
Updated this to |
getBreadcrumbs()
on scope to abstract this away_getBreadcrumbs()
on scope
Making it easier to potentially change this e.g. for POTEL.
Making it easier to potentially change this e.g. for POTEL.
Making it easier to potentially change this e.g. for POTEL.