Hi,
On Sun, 27 Aug 2023 at 20:25, Adam Faiz wrote:
> Must the 'computed-origin-method' workaround be solved by adding the
> renaming capability to snippets?
>
> Why couldn't the file-name field of the source origin be used to
> rename it?
>
> If it's because the upstream source might be confused
Hello everyone,
I'm wondering about the solution to the computed-origin-method workaround...
Must the 'computed-origin-method' workaround be solved by adding the renaming
capability to snippets?
Why couldn't the file-name field of the source origin be used to rename it?
If it's because the upst
