Should IsSavable include IsChild and EditLevel?

Should IsSavable include IsChild and EditLevel?

Old forum URL:

ngm posted on Saturday, February 02, 2013

I noticed that IsSavable does not mirror checkes that Save / SaveAsync method performs. Those are IsChild and EditLevel property checks in particular.

It seems that the object could report that it's savable even though invoking Save on it will fail.

As far as IsChild goes, this can be pretty fine behavior if IsSavable indicates whether the object is savable directly or through its parent.

I'm not quite sure that I see any benefits by omitting EditLevel check from IsSavable.

Either way, it would be nice to have centralized polimorphic property that indicates whether Save method can be invoked on the particular object.

Any background on this topic?


- ngm


Copyright (c) Marimer LLC