Could use config.exs (ie dev.exs) for the config instead of creating a config file? about plsm HOT 4 CLOSED

When I started this project I had about 2 weeks of Elixir experience (if that) so I definitely didn't do this the "elixir way". Moving this to a more proper "Elixir way" of doing things makes a lot of sense and can only help the project. That being said, it is going to be important to maintain backward compatbility with the old config files. Going forward there may not be any new changes to generating the config file but we should always be able to read it (at least 'til version 2.0)

from plsm.

Heh, well this project is awesome, my own implementation ages ago that I wrote as a hack imported from Postgres via functions, so this is really good :) (I've since lost this, thankfully :)).

Yeah, keeping both ways (when implemented) until some arbitrary point (as you said, 2.0 or whatever) is a great option.

from plsm.

Thanks, I'm glad you feel that way! I'll start moving to the config.exs file and away from the custom config file

from plsm.

This is in version 2.0.0

from plsm.