Skip to content

Conversation

@mattieweathersby
Copy link
Contributor

I was struggling with recognizing Java data types when looking at JSON values, especially telling the difference between numbers, text, and true/false values. At first, I could spot Strings, ints, longs, and booleans, but I got stuck when it came to identifying float vs double.

What I learned is:
Strings always have quotes "...".
Integers (int/long) are whole numbers without quotes.
Booleans are true or false.
Floats vs doubles both handle decimals and scientific notation (E), but Java defaults to double unless you add an f at the end.
Double is the big jug, while float is the small cup.

Where I still may need some help is building the instinct to quickly decide between int vs long, and to practice spotting when to use float vs double in real programs (not just in theory).

Copy link
Contributor

@anthonydmays anthonydmays left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎓 Automated Grading Report

Student: Mattie Weathersby
Date: 8/26/2025

Feedback

Mattie Weathersby has submitted a DataProvider implementation and a corresponding JSON file. Functionally, the submission meets most of the requirements by providing a getColumnTypeByName method that maps column names to data types. However, there are mismatches between the data types in the Java code and the JSON file. For example, column1 is mapped to Short.class in Java, but the JSON values exceed the range of a short. Similarly, column3 is mapped to Double.class, but the JSON values are formatted as strings representing doubles, which is correct, but the comment in the code suggests a misunderstanding. Technically, the Java file name does not follow proper naming conventions; it should be MattieWeathersbyProvider.java with a capitalized class name. Additionally, the comments in the code suggest confusion about the data types. The GitHub checks have passed, indicating the code compiles and runs, but attention to naming conventions and type accuracy is needed. No stretch criteria were attempted, so the stretch score is not applicable. Overall, the submission demonstrates a good attempt but requires refinement in understanding data types and adhering to naming conventions.


This is an automated preliminary review. Please review and adjust before finalizing.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants