added #int reader

[source-c]

for native Java services there are a lot of cases when numeric have to be strictly passed as integer. to avoid manual handling such needs #int reader to be added.

[codecov-commenter]

Codecov Report

Merging #101 (e13104b) into master (743e9bc) will increase coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #101      +/-   ##
==========================================
+ Coverage   79.13%   79.24%   +0.11%     
==========================================
  Files           4        4              
  Lines         369      371       +2     
  Branches       17       17              
==========================================
+ Hits          292      294       +2     
  Misses         60       60              
  Partials       17       17              

Impacted Files	Coverage Δ
src/aero/core.cljc	74.68% <100.00%> (+0.21%)	⬆️

---

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 743e9bc...e13104b. Read the comment docs.

[olymk2]

Any chance this can be merged ? just hit this myself configuring a db pool

DB_POOL_MAX_SIZE is read as a string but not accepted by https://github.com/brettwooldridge/HikariCP

:pool-opts {:maximumPoolSize #or [#env "DB_POOL_MAX_SIZE" 3]}

[source-c]

Hello. Is there a chance the request become merged?

[source-c]

Any chance this can be merged ? just hit this myself configuring a db pool

DB_POOL_MAX_SIZE is read as a string but not accepted by https://github.com/brettwooldridge/HikariCP

:pool-opts {:maximumPoolSize #or [#env "DB_POOL_MAX_SIZE" 3]}

You are welcome to use https://github.com/dkdhub/edn-config instead. It is a drop-in replacement with #int reader enabled out-of-the-box.

[joelittlejohn]

Seems fine to add an #int reader as we have #long and #double.

I don't like, however, that this allows two different ways to specify the int value in the edn: as an int or a string. This is a surefire way to make config inconsistent, with different styles used in different places, and engineers not being sure how they're supposed to specify values. Every other value is specified as a string, so we should stick with that.