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.

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

catch bad data types in calculations #132

Open
getodk-bot opened this issue Nov 2, 2011 · 0 comments
Open

catch bad data types in calculations #132

getodk-bot opened this issue Nov 2, 2011 · 0 comments

Comments

@getodk-bot
Copy link
Member

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)


http://code.google.com/p/opendatakit/issues/detail?id=356

if you add a calculate="200 div 100" to an geopoint (or a integer) node, there will be class cast exception at some point because that calculation isn't valid. ideally these kinds of problems should be caught by the parser.


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

No branches or pull requests

2 participants