Refactor: Move Field generation responsability to Resource

[sdurban]

Coming from #64 .

Well I think the best place for generating Field object is in the every Resource (Connection handler), since every resource will be having their own conversions, what do you think?

@koxudaxi I normally don't code in Python so if something is "bad practice" just tell me.

[codecov]

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #66   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           13        13           
  Lines          635       648   +13     
  Branches        79        79           
=========================================
+ Hits           635       648   +13     

Impacted Files	Coverage Δ
local_data_api/models.py	100.00% <ø> (ø)
local_data_api/resources/jdbc/__init__.py	100.00% <100.00%> (ø)
local_data_api/resources/jdbc/mysql.py	100.00% <100.00%> (ø)
local_data_api/resources/jdbc/postgres.py	100.00% <100.00%> (ø)
local_data_api/resources/mysql.py	100.00% <100.00%> (ø)
local_data_api/resources/postgres.py	100.00% <100.00%> (ø)
local_data_api/resources/resource.py	100.00% <100.00%> (ø)
local_data_api/resources/sqlite.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6107892...cd4d6d9. Read the comment docs.

[koxudaxi]

@sdurban

Well I think the best place for generating Field object is in the every Resource (Connection handler), since every resource will be having their own conversions, what do you think?

I agree It's very great.

@koxudaxi I normally don't code in Python so if something is "bad practice" just tell me.
no problem 👍

The version has been released as 0.4.13
Thank you for refactoring a lot of code 😄