feat: CSVReader typescript improvements | style object type casting refactoring

[berkinanik]

resolves #149

• properly typed useCSVReader hook and CSVReader component.
• updated examples on CSVReader usage.
• style object type refactoring by removing unnecessary CSSProperties casting.
• Additional fix on no console logs on local file examples on demo page.

might be considered as a breaking change proposal

Important parts are under: useCSVReader.tsx

[berkinanik]

• Generic element types (HTMLDivElement or HTMLButtonElement) used for root and clickable remove elements which allow getRemoveFileProps and getRootProps to be properly types are added for useCSVReader.
• Return types are updated for the hook, ProgressBar and Remove components as ComponentType which allows proper prop intellisense while using the components.
• Event handler functions are generically typed using that generic element type for proper event handler types and event types. No more explicit event type definition is required.
• ParseResult fn is updated so result is properly typed. Its object attributes can now be viewed using intellisense.

[berkinanik]

js-docs for useCSVReader hook

---

useCSVReader hook returns the properly typed CSVReader component

generic element type provides proper event handler, event and children render function's arguments proper types

first generic type is the parsed result's data type which affects return result type

---

results object is now properly typed as ParseResult and thanks to properly type CSVReader and the hook. Its type is inferred using the handler onUploadAccepted functions argument type

---

Thanks to properly typed children render function arguments and all the return types of those argument methods, now children render function is properly typed and proper types are inferred

Inferred types of those renderer func arguments, all that methods return proper props of the elements for the spread operation

---

All the events themselves and the handler function types are properly inferred

[statusunknown418]

why hasn't this been merged yet :(

[antoinerousseau]

Thanks @berkinanik ❤️

@Bunlong can we merge this? it's awesome

[spencemc]

This would be awesome to merge! @Bunlong

[jjjjonathan]

Any blocker here? @Bunlong would love to have this