mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #59] (possible regression bug) Tag list not shown in (<tag>), [<tag>], (<tag>:1.2) syntax #43
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
low priority
low priority
pull-request
question
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DominikDoom/a1111-sd-webui-tagcomplete#43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @byzod on GitHub (Nov 1, 2022).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/59
Tagcomplete version:
github.com/DominikDoom/a1111-sd-webui-tagcomplete@92a08205d0Editing tag in weight parenthesis and no tag list shown, different from the demo here.
Editing tag in simple weight syntax (

(<tag>),[<tag>]) and no tag list shown unless blanks before and after the tag.When edit
catin(cat)(alias of(cat:1.1)), it searchs(cat)exactly, only tags likechen_(cat)matches butcat_earsdo not.discussion: tag can and many of them do have parenthesis, but that's not needed when speaking of searching at most of times, for example
cathave hundreds of related tags while(cat)is a valid tag component too but have only 9 matches out of 10k tags.So maybe it's safe (or to say tolerable) to ignore parenthesis of user input?
@DominikDoom commented on GitHub (Nov 1, 2022):
You are correct, seems to be a regression introduced by an oversight in
e49862d422.It's an easy fix luckily, will push it in a moment.
Problem is that with the current way I replace/insert the completed text, it needs to match what the user typed 1:1, else it won't find what region to replace. So if we ignore parentheses while typing, replace will likely not work, and an "approximate match" is pretty hard to do properly.