Skip to content

fix: make enable_meta_sniffer behavior consistent with CUSTOM_FALLBAC…#5006

Open
rz467fzs7d wants to merge 1 commit intovernesong:devfrom
rz467fzs7d:fix/preserve-sniffer-config-dev
Open

fix: make enable_meta_sniffer behavior consistent with CUSTOM_FALLBAC…#5006
rz467fzs7d wants to merge 1 commit intovernesong:devfrom
rz467fzs7d:fix/preserve-sniffer-config-dev

Conversation

@rz467fzs7d
Copy link
Copy Markdown
Contributor

fix: unify behavior when custom config options are unchecked

CUSTOM_FALLBACK_FILTER and ENABLE_META_SNIFFER have the same frontend interaction:
both use a checkbox to control whether to use YAML custom config.

However, their default behaviors are inconsistent when unchecked:

  • CUSTOM_FALLBACK_FILTER=0: respects YAML config
  • ENABLE_META_SNIFFER=0: forces sniffer to be disabled

This fix makes them consistent: when unchecked, always respect the YAML config file settings.

…K_FILTER

CUSTOM_FALLBACK_FILTER and ENABLE_META_SNIFFER have the same frontend interaction:
both use a checkbox to control whether to use YAML custom config.

However, their default behaviors are inconsistent when unchecked:
- CUSTOM_FALLBACK_FILTER=0: respects YAML config
- ENABLE_META_SNIFFER=0: forces sniffer to be disabled

This fix makes them consistent: when unchecked, always respect the YAML config file settings.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@rz467fzs7d
Copy link
Copy Markdown
Contributor Author

也可以遵循 SNIFFER 的控制逻辑,独立一个 ENABLE_FALLBACK_FILTER 来控制,逻辑上更清晰 ; 你们的想法呢?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant