Better validation on Intergers / ID

[xrow]

Hi,

we noticed that we had looping or nerver ending scripts runs due formetting error. A little input validation would be beneficial.

works:
`

mode: update

type: location
match:
    parent_location_id: 297266 #297266 /Blogs/Markenschau/Marken
parent_location_id: 102 # /Marketing
sort_order: DESC

doesnt work:
`-
mode: update

type: location
match:
    parent_location_id: 297266 #297266 /Blogs/Markenschau/Marken
parent_location_id: 102 /Marketing
sort_order: DESC

`

[gggeek]

Note that we can only validate content/location ids to be positive integers values when setting them.
When using them for matching, the code tries to be smart and in many places will treat a string value as remote_(content/location)_id.

Apart from that, ok.

Unless we think that in the future the eZ APi might allow non-integer IDs...

[gggeek]

Update: it seems that eZPlatform API is being tightened to only accept integers for Id fields. Will have to check how this impacts the migration bundle - it will probably have an effect on this request...

[gggeek]

ps: going forward you will be able to use expect: one or expect: many when you want to make sure that your update/delete migrations do act on a item (it's already in master, to be released as 5.13)