-
Notifications
You must be signed in to change notification settings - Fork 38
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
quantifying wildcard - breaking change #50
Comments
i.e. it is populated to It's just that some parts of the documentation are incorrect. It should be
|
Btw, I updated Impact Pack to support |
Thanks a lot :3 |
Sorry for coming back on this issue, would it be possible to add a "comma" by default as a separator ? I feel like it was forgotten ^^" |
Please revert your change with "quantifying wildcard" which say to use the synthax "$$count#wildcards".
This is a breaking change for me who write and publish wildcards, specially since this a diverging implementation from wildcard plugins for other web-ui such as https://github.com/adieyal/sd-dynamic-prompts/blob/main/docs/SYNTAX.md
The result is this prompt won't call twice the wildcard as it did before:
{2$$cornf-fantasy-house/surrounding}
By the way the new synthax does not work as intended, or it is not intuitive, or the example given in the documentation is wrong :
{2$$, $$5#wildcards} turns into {2$$, $$wildcards|wildcards|wildcards|wildcards|wildcards}
The text was updated successfully, but these errors were encountered: