chore(sticker-catalogue,web-frontend): fix quarkus compose build issue and broken frontend in E2E tests#214
Merged
Merged
Conversation
3 tasks
a68c3cd to
f3283f2
Compare
scottgerring
commented
Feb 16, 2026
scottgerring
commented
Feb 16, 2026
scottgerring
commented
Feb 16, 2026
jeastham1993
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Couple of things to get the builds going again. Commits are broken down accordingly.
Update quarkus - which pulls in new testcontainers version that fixes the "broken by the passage of time" docker issue.
Fix UI - some changes I think largely from the print service subtly broke some bits in the UI. To resolve:
AuthProviderdoesn't load its children until auth state has resolved; previously we could render even ifisLoadingwas true, which would mean we'd have components loading before user data was available. I'd rather just block until we have it, as it makes everything downstream simpleruseEffectinto two; one to fetch the sticker details (doesn't need user ID), and one to that checks ownership, that is. This reflects the reality of the auth model which allows access to sticker details without auth (e.g. for public page)isLoadingcheckFix E2E tests - changed the "Sticker Collector" check to match against the role, now that we're not showing Sticker Collector there anymore. I'm not sure if listing the role in the sidebar makes sense, but this aligns the test with behaviour at least.