Improve chest blueprint mechanics

[Warger]

TL;DR

there are what feels inconsistent interactions between chests set for upgrading and blueprints pasted on top of them.

What ?

I am not sure if this is a bug, an oversight or an intended behavior, however i think this is the most appropriate section.
The problem is that there are inconsistent mechanics when blueprinting chests on top of other chest that have been upgraded (but not yet placed) with an upgrade planner. A few examples are here:
when i upgrade an iron chest to a steel chest (request for upgrade set, the chest is still iron) i can copy paste another steel chest on top of it and it changes the limit of the chest to the one i copypasted.
If i switch to a storage chest (iron -> storage upgrade request) i can copy paste a different storage chest but it doesn't copy all the settings. only the limit gets copied, not the filter for the storage chest.
The same thing happens with different kinds of chests that have more options than just a limit.

Why ?

In my opinion it feels like this is an inconsistent behavior in the blueprinting mechanics, since only half the settings get copied. Especially since it was added that copying an entity with an upgrade request on it gives the upgraded item in the generated blueprint. So if the item set for an upgrade request is treated as the upgraded item when copying it, why would it not be treated as the upgraded item when pasting the same item on it?

https://youtu.be/-tFRVBnqBDI video demonstrating what i mentioned above.

[ssilk]

So what do you suggest? How should this behave in your opinion?

[Warger]

Sorry, i forgot to properly word the suggestion and i wrote the earlier post like a bug report rather than a suggestion.
I would like to have either all or none of the settings of the blueprinted chest copied onto the one one set for upgrade. Having only some of the settings copied is counterintuitive and it doesn't feel right. Personally i would strongly prefer if all of the settings were copied since entities set for upgrade behave already like the upgraded entity when you copy them.

BTW on a side note this happens also with inserters set to be upgraded to filter inserters. The stack size limit immediately gets applied, but for the filter you have to wait until the filter inserter is actually placed.