Is it best practice to name inputs more generically? eg. :employee/id, :album/id etc.? Whereas the output should be more descriptive… eg. :employee-of-the-month/id, :favorite-album/id . And sort of related, is there a way in EQL to map/join one to the other, or is it only through alias/resolver?
I asked a similar question before and got some great feedback that may be helpful to you https://clojurians.slack.com/archives/C87NB2CFN/p1649444214808479
@alex.sheluchin Actually already watched those videos and read the thread. I’m feeling like “if the input represents the same thing” then I should be good, which for us I think it generally does.
https://github.com/souenzzo/eql-style-guide?tab=readme-ov-file#global-namespaces
@souenzzo what a great resource, I've never seen that document before. I'm wondering if any of your thinking on these points has evolved since your last edit four years ago.
Unfortunately, I no longer use pathom in my work. contributions are very welcome. questions and discussions too 🙂