[FLOW3-general] Single table inheritance and property mapper

[Robert Lemke]

Hi Helmut,

On 11.11.2012, at 17:21, Helmut Hummel <helmut.hummel at typo3.org> wrote:

> I have not checked, but I assume it's the same in Flow currently.

correct.

> Would it make sense to render the object type in a hidden field and use this information in the property mapper?
> Security might be an issue here, but this can be easily handled by hashing this information.
> 
> Is this a valid usecase?
> 
> Any other ideas (except writing different actions, which would of course work)?


If there's a water-proof (=secure) solution which allows submitting a "type hint" through a hidden field then yes, that
could be an option. Question is if it unnecessarily raises the complexity which might lead to confusion or bugs.

Does using two different actions really feel so bad?

Cheers,
Robert

-- 
Robert Lemke
Lead Developer TYPO3 Neos and TYPO3 Flow
Co-Founder TYPO3 Association

Blog: robertlemke.com/blog
Get involved: typo3.org – flow.typo3.org – neos.typo3.org