Menu

#122 Empty strings should be preserved

open
nobody
Priority (41)
2017-01-20
2017-01-11
Anonymous
No

Originally created by: cjmyers

If an object is an empty string (i.e., just a tag), it should be preserved as an empty string and not dropped.

Discussion

  • Anonymous

    Anonymous - 2017-01-17

    Originally posted by: bbartley

    This requires non-trivial refactoring of code and will delay release. Are there any compelling use cases where empty strings are critical? Currently some test files are failing because a Sequence elements property is set to "". In these cases the Sequence objects seem to contain no data are superfluous.

     
  • Anonymous

    Anonymous - 2017-01-18

    Originally posted by: cjmyers

    I think this could be delayed to the next release, but I do think this fix should be done. Again, it comes down to not changing data during a read/write roundtrip. Furthermore, for the examples that have this, it changes a valid model into an invalid one, since the elements field is required in a sequence. So, this is not good either.

    Correct me if I’m wrong, is the problem that your code cannot distinguish between an empty string and no string at all? Is it not possible to initialize strings to “null” rather than an empty string? In libSBOLj, we have isSet methods, and they will return true for empty string and false for null string.

    On Jan 17, 2017, at 10:30 PM, bbartley notifications@github.com wrote:

    This requires non-trivial refactoring of code and will delay release. Are there any compelling use cases where empty strings are critical? Currently some test files are failing because a Sequence elements property is set to "". In these cases the Sequence objects seem to contain no data are superfluous.


    You are receiving this because you authored the thread.
    Reply to this email directly, view it on GitHub https://github.com/SynBioDex/libSBOL/issues/122#issuecomment-273321586, or mute the thread https://github.com/notifications/unsubscribe-auth/ADWD98Moj1FzxvyEZtrXSSNhtKzYZ6o5ks5rTUEYgaJpZM4LhMKG.

     

Log in to post a comment.

MongoDB Logo MongoDB