Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Do not set min/max values to empty string #46

Closed
ctrueden opened this issue Jun 25, 2014 · 2 comments
Closed

Do not set min/max values to empty string #46

ctrueden opened this issue Jun 25, 2014 · 2 comments
Milestone
0.3.1

Comments

@ctrueden
Copy link
Member

When there is no min or max, an empty string is being set as the min/max by imagej-omero. This causes problems with OMERO.

See http://trac.openmicroscopy.org.uk/ome/ticket/11472 for additional details.
@ctrueden ctrueden added this to the 0.1.1 milestone Jun 25, 2014
@ctrueden ctrueden self-assigned this Jun 25, 2014
@ctrueden ctrueden assigned bramalingam and unassigned ctrueden Apr 17, 2015
@ctrueden
Copy link
Member Author

Thanks @joshmoore for ome/openmicroscopy@26bf13f, which made it really obvious (now that I finally got around to investigating this bug again) which fields had non-null mins and maxes. It was indeed the string fields return "" for min and max, rather than null as expected.

@ctrueden
Copy link
Member Author

See also #59, which will reenable the min/max parameter population, once scijava-common 2.41.1 is released.

@ctrueden ctrueden modified the milestones: 0.3.1, m1-bugs Jun 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.3.1
Development

No branches or pull requests
2 participants
@ctrueden @bramalingam