The streams in "Streams"/"onInsert" config field should probably not be deletable by users. The server should guard against this, and should report the impossibility in $stream->exportArray() even to publishers. The client should consult stream.access even if the user is a publisher of the stream.
On the other hand, today we can't really "delete" streams but just "close" them, which disconnects all the relations and marks them for deletion. We could just assume the system will always be like this, and not delete those streams. But, it's better for clients to know that they can't really delete those streams, and not show the "x" for example in Streams/preview/tool. Thus, the first solution is better.
The streams in
"Streams"/"onInsert"config field should probably not be deletable by users. The server should guard against this, and should report the impossibility in$stream->exportArray()even to publishers. The client should consultstream.accesseven if the user is a publisher of the stream.On the other hand, today we can't really "delete" streams but just "close" them, which disconnects all the relations and marks them for deletion. We could just assume the system will always be like this, and not delete those streams. But, it's better for clients to know that they can't really delete those streams, and not show the "x" for example in
Streams/preview/tool. Thus, the first solution is better.