Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Spike: Support for required metadata

Open
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Start with the feature create command and reproduce the required-metadata failure shown in the issue. Inspect the other commands that create or update resources to identify which are affected, then review the existing design documentation. Done means the affected command scope is documented and the metadata-support design is updated.

Written by the indexing model from the issue text.

Description

In a project with required metadata fields, flagsmith feature create always fails:

$ flagsmith feature create cli_max_items --value 25 --yes
Error: POST https://api-staging.flagsmith.com/api/v1/projects/6111/features/ returned 400 Bad Request: Missing required metadata field: Required int field
Think this shouldn't happen? Tell us: https://github.com/Flagsmith/flagsmith-cli/issues/new

feature create has currently no way to send metadata.

We should spot all the commands this affects, and update design documentation with metadata support

Dominant language
Go
Stars
12
Forks
3
Avg merge
2h 35m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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 Flagsmith/flagsmith-cli

All issues in Flagsmith/flagsmith-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.