Remote protocol type validation for strict mode class #1429

Closed
CJdeVos opened this Issue Apr 8, 2013 · 1 comment

Comments

Projects
None yet
4 participants
@CJdeVos

CJdeVos commented Apr 8, 2013

When specifying values for fields it seems as if default values are inserted when the passed value is not of the correct type. I would however expect either an OSerializationException or OValidationException.
Consider the following:

  • LINK field: Put a numeric, string or array value. A NULL value is inserted. An exception was expected.
  • LINKSET: Accepts [#8:0, #8:1, (OTHERCLASS@A:"B")] but throws errors in the console.
  • BOOLEAN: accepts ANY value but only puts it as true when the value is actually true.
  • EMBEDDED: accepts ANY value but puts NULL when it is not an embedded document.
    For any of these (and more...) cases I would have expected errors to be thrown because it's being asked to use values which are not accepted by the strict class.

@lvca lvca added this to the 2.0 Final milestone Oct 3, 2014

@lvca lvca added the enhancement label Oct 3, 2014

@tglman tglman modified the milestones: 2.1, 2.0 Final Oct 13, 2014

@lvca lvca modified the milestones: 2.2, 2.1 Feb 1, 2015

@lvca lvca modified the milestones: 3.0, 2.2 Apr 14, 2015

@tglman

This comment has been minimized.

Show comment Hide comment
@tglman

tglman Apr 15, 2015

Member

this isn't true anymore, since 2.0 the value are converted on set or an exception is thrown.

closing

Member

tglman commented Apr 15, 2015

this isn't true anymore, since 2.0 the value are converted on set or an exception is thrown.

closing

@tglman tglman closed this Apr 15, 2015

@tglman tglman added the wontfix label Apr 15, 2015

@robfrank robfrank modified the milestones: 3.0, 3.0-M1 Apr 12, 2017

@lvca lvca modified the milestone: 3.0-M1 Aug 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment