| Summary: | Feature request: Regular expression based project filters | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Alex Lowe <lengau> |
| Component: | file tree | Assignee: | kdevelop-bugs-null |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | igorkuo, lengau |
| Priority: | NOR | ||
| Version First Reported In: | 5.10.221202 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Alex Lowe
2023-02-20 21:25:31 UTC
Wouldn't having both syntaxes be confusing? One more column with the syntax choice would have to be added. I suspect the rare regex use case doesn't justify the effort, code and UI complexity increase. Porting to QRegularExpression is welcome. But it is not straightforward, because QRegularExpression::wildcardToRegularExpression() does not match slashes with '*'. See the discussion here: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/439#note_623331 So we need to deal with this general issue before porting individual wildcard QRegExp uses. |