I selected a bunch of cards and moved them to an existing space. In the UI, after hitting the Move button, the spinner just keeps spinning. I examined the console and saw this error. In a separate browser, I verified that the cards do show up in the destination space.
ah there was a bug where this would fail if the destination space wasnāt already locally cached, added a fix for this
while iām here, to reduce upfront complexity, iām also going to remove the āswitch to spaceā option and add that to the success notification
wip:
I think thatās a good improvement. that choice on whether to switch to the new space or not always slowed me down and I was never sure which one I wanted. leaving you in your current space and presenting the option to go to the new one upon success is the right move ā thank you!
ya thatās been my experience too,
wondering if this additional layout streamlining would also help:
before:
after:
thoughts? whatās easier to understand at a glance?
I see how the second one is more streamlined with less redundant information (one less āMoveā). Itās hard to say which one is easier to understand at a glance, might be about the same.
But studying it a bit more, I wonder if there are other opportunities for streamlining. For example, the destination space name is still mentioned twice. You could possibly get rid of the āSpace / ļ¼ New Spaceā toggle, and just have the space browser dropdown be after the āToā. Or not get rid of, but integrate the name selection into that toggle? just some thoughts, if I think of more concrete ideas I will share them 
1 Like
makes sense but moving the new space into a list of spaces is a whole big scope up so Iāll leave it alone for now and ship just with the streamlined āswitch to spaceā removed
1 Like
yup, I was going to mention that too in my message. I realize I was blowing up the scope and donāt want you to feel like Iām asking for that improvement 
1 Like