open-feature / open-feature/flagd
[FEATURE] Parse Array of `flags` Objects From All Sync Sources
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
[FEATURE] Parse Array of flags Objects From All Sync Sources
Background
flagd needs to support flags defined in an array, as well as the previous map format.
Requirements
- Flags must be parsed, and stored in memory, annotated with both their
flagSetId(nilis a possible flagSetId) as well as theirsource - Refactors to the underlying storage layers are encouraged (this was mostly done with (https://github.com/open-feature/flagd/pull/1697).
- Particular care should be taken to make retreival of sets of flags based on their flag set efficient and easy
- Associated tests
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with parent issue #1671 and the storage-layer refactor in pull request #1697, then inspect how each sync source parses and stores flags. Focus on efficient flag-set retrieval and add the associated tests; done means array-form flags work across all sync sources with flagSetId and source annotations preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100