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
Please describe the feature you have in mind and explain what the current shortcomings are?
Currently the expected filepath for AOVs that are separate files are hardcoded.
This would be follow-up on #72 and in particular to resolve the points mentioned in this comment.
How would you imagine the implementation of the feature?
AOV with separate files enabled should be allowed to render to custom filepaths/names and be supported by the publishing logic regardless of where they are.
Are there any labels you wish to add?
I have added the relevant labels to the enhancement request.
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Currently the expected filepath for AOVs that are separate files are hardcoded.
This would be follow-up on #72 and in particular to resolve the points mentioned in this comment.
How would you imagine the implementation of the feature?
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: