You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently saving the config includes the complete list of regex patterns
This probably isn't too good, as most of the time people a) wont change them, or b) won't remove that option and this wont pick up improvements to the default patterns
Instead the default patterns should be moved out of the config, and instead:
New option to add custom patterns.
Need a way to control if these patterns are checked before or after the built-in patterns
Need a way to control if the custom patterns completely replace the built-in ones or not (e.g someone might only want to match a very strict set of patterns)
Should use v4.0 to deprecate the filename_patterns option - keep respecting it for now, but emit warning that this option will be removed soon
The text was updated successfully, but these errors were encountered:
Most flexible way would be to have a custom_patterns = {'pattern': '...', order: '...'} or something, but that seems a bit clunky
Instead maybe just:
A custom_patterns config option, default empty, with a list of regexs
A second option, something like custom_patterns_order which can be either before, after, or replace (i.e before builtins, after builtins, or replace them entirely). Default would probably be "before".
This makes it easy to just add one or two custom patterns, and either prefer them tot eh builtins, or use them as a fallback. The "replace" option would be useful to customize the pattern matching in more complex ways (or only handle a very specific set of patterns)
Currently saving the config includes the complete list of regex patterns
This probably isn't too good, as most of the time people a) wont change them, or b) won't remove that option and this wont pick up improvements to the default patterns
Instead the default patterns should be moved out of the config, and instead:
Should use v4.0 to deprecate the
filename_patterns
option - keep respecting it for now, but emit warning that this option will be removed soonThe text was updated successfully, but these errors were encountered: