Support registering global traits at client initialization

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start by locating the Python client initialization and evaluation methods, then trace how per-call traits are currently passed. Define an initialization option for global traits and verify that evaluations include them by default while still accepting per-call traits. Done means consumers no longer need a wrapper or manual merge for traits that remain constant.

Written by the indexing model from the issue text.

Description

Summary

Some traits are global and never change for the life of a client, for example app name and developer branch. Today they must be supplied on every evaluation call. Consumers work around this by wrapping the client to register global traits and merge them with per-call traits at runtime.

Requested feature

A way to register global traits once at client initialization so they are included in every evaluation by default, removing the per-call merge or custom wrapper.

Dominant language
Python
Stars
24
Forks
12
Avg merge
15h 43m
Merged PRs (30d)
4

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 Flagsmith/flagsmith-python-client

All issues in Flagsmith/flagsmith-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.