Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔊 Add config option for responses_without_block #293

Merged
merged 2 commits into from
Jun 15, 2024

Conversation

nevans
Copy link
Collaborator

@nevans nevans commented Jun 12, 2024

(Note: #291 is a prerequisite for this.)

This was extracted from #93 and #97, and split into a separate PR.

A new config option is added: responses_without_block. This is provided as a workaround, until dependant projects can update their usage. For now, it is set to :silence_deprecation_warning, but it will be set to :warn in v0.5 A future release may remove this backwards compatibility, but no sooner than v0.6.

@nevans nevans changed the title 🔊 Add config option for responses_without_block 🔊 Add config option for responses_without_block Jun 12, 2024
@nevans nevans added this to the v0.5 milestone Jun 13, 2024
@nevans nevans force-pushed the config-responses_without_block branch 2 times, most recently from 4a96fa2 to 22b0ef3 Compare June 15, 2024 01:50
nevans and others added 2 commits June 14, 2024 22:20
This was extracted from #93 and split into a separate PR.

A new config option is added: `responses_without_block`.  This is
provided as a workaround, until dependant projects can update their
usage.  A future release may remove this backwards compatibility, but
_no sooner_ than v0.6.
An `enum` type was added to Config::AttrTypeCoercion, to be used by
other future config options.
@nevans nevans force-pushed the config-responses_without_block branch from 22b0ef3 to ca8e26d Compare June 15, 2024 02:22
@nevans nevans merged commit 5f12016 into master Jun 15, 2024
26 checks passed
@nevans nevans deleted the config-responses_without_block branch June 15, 2024 02:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant