Skip to content

Conversation

@JThramer
Copy link

🎟️ Fixes issue
πŸ“œ Design Doc: link if applicable

Motivation and Context

When initializing offline, it may be desirable to attempt to load a cached configuration from the configuration cache. This is not possible to do manually by the client-developer.

Description

Fixing issue where it was impossible to manually loadInitialConfiguration, because configurationStore was an internal variable.

How has this been documented?

  • I don't have access to your internal tools, so you'll have to take care of that.

How has this been tested?

  • Tested on SeatGeek.app

Fixing issue where it was impossible to manually loadInitialConfiguration, because configurationStore was an internal variable
Copy link
Contributor

@petzel petzel left a comment

Choose a reason for hiding this comment

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

The ConfigurationStore is intentionally private, as we do not want to expose internals (whose implementation details may change) publicly.

@JThramer can you explain in more detail what you're trying to achieve?

@JThramer
Copy link
Author

@petzel that's sensible, I don't mind if persistent cache for configurations is handled for me, but the core issue is that the persistent cache is broken when you initialize offline, regardless of what you specify as the withPersistentCache argument in initializeOffline.

The feature looks like it works in the async initializer, but we can't use that due to technical constraints.

Does this make sense? Happy to answer any more questions.

@typotter typotter requested a review from petzel November 20, 2025 21:38
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.

2 participants