I think something like that would be reasonable… though I suppose realistically that would just be an “orphans” bag. At current, my general impression is that they default to whichever tiddler is top of the recipe they are imported into, if you are using the traditional import features. I hesitate to think that deleting a bag necessarily deletes all tiddlers in that bag: I think it makes sense to have some kind of default “catch” where tiddlers end up if they are not explicitly deleted.
I don’t know if I was really having success changing bags by changing the field values, or if I was given that false impression because I was resorting the recipe.
I personally am a big fan of the idea of moving from one bag to another by changing the field value, but after some experimentation yesterday I am not so sure that will be possible, and I think pursuing direct changes to the database is going to be the strategy. This leads me to wonder if the bag field is truly vestigial at this point.
Instead I have modified the post-bag-tiddlers.js to also handle move operations and added a form to the bottom of get-bag.tid which allows the user to move tiddlers from one bag to another:
It currently requires the user to add the title manually and does not accept arrays – once I figure out how to make the checkbox functionality work with it and implement arrays, I’ll make a PR.