# Hex description: "A toolkit for data mapping and language integrated query for Elixir", package: package(), # Docs name: "Ecto", docs: docs()
Whereas you can see some folks labeled some keys under some comment for an obvious reason; since those keys are actually correlated to each other and actually belongs to specific tools that use them.
I also suffer from these organization on my projects which I copy-paste the structure of the project config pretty much.
I would propose to actually enforce (not sure how or if this is a right move) or at least be disciplined when it comes to adding keys under project config. Since avoiding conflicts or adding complexity when it comes to understanding all these keys.
Situations like this one, I would prefer to move
package key and
Maybe synchronize with the authors of those packages and deprecate the global keys since both of them belongs to Elixir Core and Hex Core, should be easy to synchronize with them.
Yes, this is not a bid deal and it works today, but I would prefer to change it today when the community is not that big to be resilient about changes.
Better to do what is right (which I could be wrong in thinking that this is the right thing to do) than pay off the cost later on because minors things like this didn’t matter but too many minor things became a big thing.
What is your opinion about it?