Implementation for global pincodes

[abhushanaj]

fixes #2

@plxity here's what the PR offers:

As discussed since the only way to achieve this would be via offline data set, I have implemented the same version in React demonstrated here.

As discussed right now the data set only includes for India and US zip codes and so it'll work only for that.

The issue about the bundle size optimization is addressed via an API as you suggested, the API not not built extremely robust it's just enough to be up and running and I have used the same to minimize bundle size.

Here's a small example for it's working:

Future Improvements which can be done:

• Improving the API
• Improving the dataset (For India it works extremely well so it can be avoided )
• The additional input to add states, so seperate json files can be kept instead of having on huge file

[yellowwoods12]

@abhu-A-J Looks good to me.

[yellowwoods12]

@abhu-A-J We need to remove multiple similar fields when one types a pincode. Like I can see multiple "Pune" in the city dropdown and similarly in state.

[yellowwoods12]

@plxity Also lets keep this to a separate testing branch since it is a completely different development for the module. We'll also encourage other participants to work on the possible improvements to this PR.

[abhushanaj]

@abhu-A-J We need to remove multiple similar fields when one types a pincode. Like I can see multiple "Pune" in the city dropdown and similarly in state.

@yellowwoods12 The repetition is due to the dataset itself. It's because the dataset has similar fields, if we use a dataset that has no repetition then that issue won't be present. It's completely dependent on the offline data used.

[plxity]

@plxity Also let's keep this to a separate testing branch since it is a completely different development for the module. We'll also encourage other participants to work on the possible improvements to this PR.

Yes, definitely.

[plxity]

@abhu-A-J You can remove duplicate fields in this too. Please make those changes then we are going to merge this PR.

[abhushanaj]

@abhu-A-J You can remove duplicate fields in this too. Please make those changes then we are going to merge this PR.

@plxity The duplicate data fields are present because the dataset itself has duplicate field. If we can get the data set with non-repetitive fields, this issue won't be present. It's not a side effect from code. You can see this here the data coming back from API endpoint created.

[yellowwoods12]

@abhu-A-J Yes we get that. What we are suggesting here is to filter out duplicate entries after you've fetched them from the API.

[abhushanaj]

@yellowwoods12 @plxity I have removed the problem for repetitive data. Here is the working now.
Hope it's okay now??

[yellowwoods12]

@abhu-A-J Good Work!

[plxity]

@abhu-A-J Can you raise this PR to the development branch?

[abhushanaj]

@abhu-A-J Can you raise this PR to the development branch?

Sure, I'll do the same, so I'm closing this PR and make a new PR to development branch.