Marc Schipperheyn
Marc Schipperheyn
Sorry, there are easy ways around this.
A workaround for the issue is to assign the to be copied entity to the target channel before copying (and removing after copying). That prevents the asset error occurring. But...
A co-worker suggested that since the assets can't really be edited and can therefore just get a channel copy, and a delete on one channel would not impact another channel...
A workaround for me seems to be to delete yarn.lock and reinstall. That seems to fix the issue each time.
As a general suggestion for the overall setup I suggest using the ability of Tailwind to set up aliases for your colors in line with Material ui, makes it easier...
I have this when I pass an empty string to a `{emptyString}` RN0.32
Could be. If you guys have a base repo I can copy and customize, that would save me the time I don't have to do it from scratch
I would suggest that you return a unique id from RNUploader.upload method, that you also pass in subsequent progress and file objects. This way, we can keep track of multiple...
What I'm doing might be considered something that wasn't considered as a common scenario but that should be possible and highlights an unnecessary limitation. IMHO
I cannot put any requirements on the backend. The backend is effectively a graphql api. So, I would like to just send a request and process the return client side....