Skip to content

Merge routing with route rule#2189

Open
veto9292 wants to merge 39 commits into
hiddify:mainfrom
veto9292:merge-routing-with-route-rule
Open

Merge routing with route rule#2189
veto9292 wants to merge 39 commits into
hiddify:mainfrom
veto9292:merge-routing-with-route-rule

Conversation

@veto9292
Copy link
Copy Markdown
Collaborator

No description provided.

veto9292 added 30 commits April 26, 2026 00:12
- Migrate IconLauncher to liquid_glass to resolve icon fading/transparency issues.
- Fix iOS build error on ARM64 simulators by correcting destination specifiers and architectures.
- Update CocoaPods dependencies and sync Podfile.lock.
- Add notifiers and data layer for the chain system
- Integrate chain options into config option repository and notifier
- Update core service to handle chain-based generation
- Connect chain preferences to application state
- Add conduitPairingId to Singbox Psiphon options for extra security and unblocker
- Implement preferences and UI for Conduit pairing ID in psiphon section
- Fix typo in extraSecurityProfileId preference key
- Add localized translations for 'Conduit pairing ID' across 10 languages
- Adhere to Material Design 3 style guide and preserve technical terms
…X; deprecating direct package selection in route rules
…ericListPage and notifier logic by eliminating the need for conversion during read/write
…utes as sub-routes of routingOptions. Also, move save logic from PopScope to onExit in the rule GoRoute.
veto9292 added 9 commits May 17, 2026 23:44
…PopScope logic (moved to onExit in routing config notifier), and update navigation and route logic
…d expandable route general options, FAB menu, and empty state for rules list and more...
…ion status changes

Temporary hotfix to resolve fatal 'setState() called during build' errors caused by lazy
evaluation of dirty provider dependency chains during high-frequency status transitions.

- Establishes eager evaluation by listening to `activeProxyNotifierProvider` at the root
  container level during bootstrap to resolve dirty state flushes in microtasks.
- Refactors `serviceRunningProvider` and all downstream dependent stream/future
  notifiers to execute synchronously to prevent build-phase timing hops.
- Defers secondary state updates using `Future.microtask()`.

Note: This is a temporary architectural patch to bypass Riverpod's lazy widget evaluation
mechanics under high-frequency stream updates. A full core communication redesign is
recommended for future maintenance to address this natively.
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.

1 participant