Handle human readable number casting in general

[mathemancer]

Problem

Currently, casting from textual types (e.g., TEXT) to numbers relies on the default PostgreSQL number handling. This will be solved for the NUMERIC type once #1107 is solved, but we should also handle other number types.

Proposed solution

We should write custom logic to allow handling casting more strings to number types.

• Casting to number types with decimals should use the same (or very similar) logic to casting to NUMERIC.
• Casting to number types without decimals (e.g., INTEGER) should use a subset of that logic that handles only grouping separators.

Additional context

This was originally inspired by the custom casting work for money types. See #1137 . This issue should complete the work begun when solving #1107 .

[mathemancer]

Marking this as blocked until #1107 is solved.

[Cronus1007]

@mathemancer I would like to work upon this issue once it gets unblocked.

[SatabrataPaul-GitAc]

HI @kgodey
Myself Satabrata Paul. a passionate backend and cloud developer from India
I would like to get started in contributing to this project , for Hacktoberfest this year . i.e. 2022
I have previously contributed to major open source projects (presently working with The Linux Foundation - LFX Mentorship)
Can we schedule a 1:1 call over gmeet ?
I just wanted to understand the code and the repository a bit better which would in turn help me pickup the issues

I am located in India (IST)
Here is my email id for reference : [email protected]

Hoping for a response soon !!!

[kgodey]

@SatabrataPaul-GitAc I don't have much time available but if you're interested in frontend work, @rajatvijay is wiling to meet with you.

[Aditramesh]

@kgodey can i work on this issue?

[kgodey]

Sure go ahead @Aditramesh

[7ashraf]

Can I have assistance on this issue, I am trying to work on this issue, where exactly in the code files should the enhancement be done?

[rajatvijay]

@7ashraf

where exactly in the code files should the enhancement be done?

This is something that you need to figure out on your own while working on the issue. Please ask more specific questions, this makes it easier and faster for us to provide help.

Also, you should look at the "Additional Context" section in the issue description. It links #1137 which should give you some headstart.

[mathemancer]

This issue is still relevant, but needs to be improved and clarified.

• The work will be blocked until casting is on the DB, since the implementation will be db-layer.
• We should have a product-level discussion about how we want users to interact with various number types before speccing this issue out

I'm going to leave it open, but block it and add some labels.