What about the case of multi-artifact content? Don’t they require separate
artifact creation and content creation routes?
David
On Tue, Feb 19, 2019 at 11:40 AM Austin Macdonald wrote:
> I think the key question to ask is:
> What circumstances would require the creation of Content that would n
I think the key question to ask is:
What circumstances would require the creation of Content that would not be
met by a one-shot upload?
On Tue, Feb 19, 2019 at 11:34 AM Daniel Alley wrote:
> @Matthias why would you prefer to keep the normal create? As you mention,
> the "orphan cleanup" issue
@Matthias why would you prefer to keep the normal create? As you mention,
the "orphan cleanup" issue applies to both, so there's no advantage given
to the former.
The normal "create" ( POST .../content/plugin/type/ ...) is unidiomatic and
inconsistent, because the fields needed to upload a conten
I have no objections to having the "one shot upload" or even "one shot
upload into repositoryversion". I think, i would like to keep the
'traditional' create anyway.
The problem i see with create and one shot upload is, that another
thing could have triggered 'delete orphans' at the wrong time, and
