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

Contexts missing from <umb-debug> #17410

Open
enkelmedia opened this issue Nov 2, 2024 · 1 comment
Open

Contexts missing from <umb-debug> #17410

enkelmedia opened this issue Nov 2, 2024 · 1 comment
Labels

Comments

@enkelmedia
Copy link
Contributor

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.3.0

Bug summary

I'm trying to debug an issue where this.consumeContext(...) never fires the callback, probably because I'm inside a modal where this context can't be consumed.

I figured that using <umb-debug visiable></umb-debug> would be a good idea so I gave it a try. It seems to work fine, but I also noticed that some contexts (most likely global once) does not show up.

image

Basically, in the same component as where I have the <umb-debug> element I'm able to consume these contexts which mean that they should probably be listed in the debug element. The screenshot from above is from inside a modal, but the same problem exists in a "regular" workspace view or dashboard.

Examples of context that does not show up:

  • UMB_CURRENT_USER_CONTEXT (UmbCurrentUserContext)
  • UMB_APP_CONTEXT (UmbAppContext)
  • UMB_THEME_CONTEXT (umbThemeContext)
  • UMB_APP_LANGUAGE_CONTEXT (UmbAppLanguageContext)
  • UMB_DOCUMENT_CONFIGURATION_CONTEXT (UmbDocumentConfigurationContext)

Seems like the common thing with all of these are that they are all registered as globalContext and hosted by the umb-app element.

Specifics

No response

Steps to reproduce

See above

Expected result / actual result

No response

Copy link

github-actions bot commented Nov 2, 2024

Hi there @enkelmedia!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant