Open demoran23 opened 1 year ago
I've done some more investigation here, and changed my prompt to fix the issue.
It was blowing up because I either didn't specify default values for parameters and then omitted them.
The updated wildcard that works as expected:
__photorealistic/style__ photo of ${subject:_},
${features:_},
${details:_},
${pose:_},
${action:_},
__photorealistic/framing__,
${setting:_},
${background:_},
__photorealistic/lighting__,
__photorealistic/camera/angle__,
__photorealistic/camera/properties/shot_on**__,
{1-$$__photorealistic/camera/properties/film_type__
|__photorealistic/camera/properties/lens__
|__photorealistic/camera/properties/filters_and_effects__},
{3::_|1::in the style of __photorealistic/photographer__}
What do you think would be a more reasonable approach to dealing with this:
I think the parameterized invocation syntax template(x=abc)
should accept multiple parameters.
The behavior of parameters should be documented
Throw an exception if any required parameters are missing that prevents the generation from proceeding
What's wrong
My prompt looks like this:
I iterated over immediate evaluation (ie ! vs no !) and invoking the prompt vs not invoking it (ie prompt() vs prompt). I'm still left with metadata that looks like this:
The promptgeek prompt looks like this:
What works
When I comment out all of the other variables besides the subject, it works as expected:
Re-enabling any of the other parameters causes the issue to happen again.
Without the actual resolved prompt being displayed, I have no idea what the prompt was that generated the image.