Conversation
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
nicklasl
commented
Sep 16, 2026
Comment on lines
+17
to
+27
| static Uri _flagEndpoint( | ||
| ConfidenceConfiguration configuration, | ||
| String operation, | ||
| ) { | ||
| final base = | ||
| configuration.resolveBaseUrl ?? | ||
| Uri.https(_host('resolver', configuration.region)); | ||
| // Preserve proxy path prefixes and append the API path exactly once here. | ||
| final prefix = base.path.replaceFirst(RegExp(r'/+$'), ''); | ||
| return base.replace(path: '$prefix/v1/flags:$operation'); | ||
| } |
Member
Author
There was a problem hiding this comment.
this is overkill. we don't need the _flagEndpoint function. just do what publish does.
nicklasl
commented
Sep 16, 2026
Member
Author
There was a problem hiding this comment.
why do we need this at all?
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: Codex <noreply@openai.com>
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.
Replace the native Flutter bridge with
confidence_openfeature_providerat the repository root. The provider resolves flags in Dart, supports synchronous typed OpenFeature reads and context reconciliation, and reports exposures only after successful reads.Migrate native visitor identity, cached flags and queued telemetry with durable import checkpoints. An atomic JSON outbox provides batching, retries and public flush; its 4 MiB budget drops the oldest unsent records. The documented trade-offs include asynchronous persistence and possible duplicate delivery after a crash. A small Foundation helper preserves legacy Swift calendar values without a native Confidence SDK dependency.
Update the public-API example, credential-free CI, migration guide and release configuration. Publishing remains disabled with
publish_to: none.Validation:
tutorial-eventacceptance pass for both Flutter SDK IDs.Generated with Codex.