beetbox / beetbox/confuse

Breaking Change in v2.2.0: Choice Template Objects No Longer Accept Iterables.

Open
#192 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
424
Forks
57
PR merge metrics
No merged PRs in 30d

Description

Choice template objects used to accept probably any Iterable. I was using frozensets. But they now require tuples (maybe lists?). Not difficult to fix, but also an undocumented breaking change.

## Workaround
Submit tuples to Choice Templates.

## Resolution Suggestion

- Document the change for people migrating
- Or restore the original ability to process Iterables like frozenset for chocies.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the v2.2.0 behavior with a frozenset passed to a Choice template, then compare it with the earlier iterable-accepting behavior. The issue leaves two possible outcomes: document the migration restriction and tuple workaround, or restore support for iterables such as frozenset. Done means one of those outcomes is agreed and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.