[BUG] Inconsistency in file provider and json parsing for different languages

Open
#1,627 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, java, json, python
Domain
backend

Research direction

Start by comparing the file-provider and JSON-parsing behavior described for flagd, Python, and Java, since the issue names no files or tests. First establish and document the agreed unified behavior for missing or incorrect information; done means the implementations follow that decision consistently.

Written by the indexing model from the issue text.

Description

bug Needs Triage
Observed behavior

Different implementations in different languages handle missing or incorrect information within the provided JSON files differently.

  • Flagd: fails if default variant or variants are not properly configured
  • Python: Fails on any missing argument
  • Java: Fails on nothing
Expected Behavior

unified behavior throughout the sdks and flagd - but what is the unified behavior?

Steps to reproduce

No response

Dominant language
Go
Stars
998
Forks
136
Avg merge
4d 8h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-feature/flagd

All issues in open-feature/flagd

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.