Although configs are a nice idea to expose customization to user, I believe it makes Sadedegel more opaque to use.
We can keep them privately to set sensible defaults (and to change them easier), however any changes should be executed by user explicitly.
As Zen of Python says:
"Explicit is better than implicit."
At the cost of a few extra lines written by user, it will bring more clarity on what is actually used.
As another, "functional" argument, it can be argued that it makes code dependent on some outside, mutable config, reducing the purity of code.
Although configs are a nice idea to expose customization to user, I believe it makes Sadedegel more opaque to use. We can keep them privately to set sensible defaults (and to change them easier), however any changes should be executed by user explicitly.
As Zen of Python says: "Explicit is better than implicit."
At the cost of a few extra lines written by user, it will bring more clarity on what is actually used.
As another, "functional" argument, it can be argued that it makes code dependent on some outside, mutable config, reducing the purity of code.