René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"All numbers are read as Float","articleBody":"When reading an excel file that is exported from other libraries, for example caxlsx https://github.com/caxlsx/caxlsx\r\nThe library generates Excel with floats and integers represented with t=\"n\", for example from the \"sheet1.xml\"\r\n\r\n```\r\n\u003cc r=\"Z2\" s=\"0\" t=\"n\"\u003e\u003cv\u003e1.0\u003c/v\u003e\u003c/c\u003e\r\n\u003cc r=\"G2\" s=\"0\" t=\"n\"\u003e\u003cv\u003e114\u003c/v\u003e\u003c/c\u003e\r\n```\r\n\r\nBoth of these numbers are read by Creek as: 1.0 , 114.0, which is causing problems when the system expects to see an integer value instead of float, for example when using that number to load Models from the Database\r\n\r\nI have found in this line https://github.com/pythonicrubyist/creek/blob/master/lib/creek/styles/converter.rb#L47\r\nThat Creek always read the value as float.\r\n\r\nMy suggestion is to replace\r\n```\r\nvalue.to_f\r\n```\r\nwith\r\n```\r\nif value.to_i.to_s == value.to_s\r\n     value.to_i\r\n else\r\n     value.to_f\r\n end\r\n```\r\n\r\nI don't know if this is the right solution or not, but by applying this as a patch in the system solved our problem.","author":{"url":"https://github.com/amhofny","@type":"Person","name":"amhofny"},"datePublished":"2021-08-25T06:29:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/100/creek/issues/100"}