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

Parsing error messages #867

Closed
keileyo opened this issue Mar 9, 2017 · 0 comments
Closed

Parsing error messages #867

keileyo opened this issue Mar 9, 2017 · 0 comments
Assignees
@nickgrippin
Labels
Parser
Projects
1.2.0
Milestone
Sprint 27

Comments

@keileyo
Copy link
Contributor

keileyo commented Mar 9, 2017

Update language in the parsing error messages:

  1. Change "Timestamp is not a Long" to "Timestamp is not an integer"
  2. Change "Integer" to "integer" in all of the error messages
  3. Change the expected fields found message from "Incorrect number of fields. found: [number], expected [number]" to "An incorrect number of data fields were reported: [number] data fields were found, when [number] data fields were expected.
@keileyo keileyo added the Parser label Mar 9, 2017
@keileyo keileyo mentioned this issue Mar 9, 2017
Closed
@jmarin jmarin added this to the Sprint 27 milestone Mar 9, 2017
@jmarin jmarin added this to TODO in 1.2.0 Mar 9, 2017
@nickgrippin nickgrippin moved this from TODO to In Progress in 1.2.0 Mar 14, 2017
@nickgrippin nickgrippin mentioned this issue Mar 14, 2017
Merged
@nickgrippin nickgrippin moved this from In Progress to Ready for code review in 1.2.0 Mar 14, 2017
@jmarin jmarin moved this from Ready for code review to Done in 1.2.0 Mar 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nickgrippin nickgrippin

Labels
Parser
Projects
No open projects
1.2.0
Done
Milestone
Sprint 27
Development

No branches or pull requests
3 participants
@jmarin @keileyo @nickgrippin