Clojurians Log v2

That’s awesome! Thanks for digging those up, @nate!

Also https://www.youtube.com/watch?v=IS3i3DTUnAI .

I find that there is a lot of nuance to consider with regards to qualified keywords. In particular, context is very important. He touches upon that at https://youtu.be/IS3i3DTUnAI?t=1741 .

For what it's worth, I've been using namespaced keys for over 3 years now and I still fine them useful in a number of situations. In particular, when I have to mix a number of fields together that come from other sources.

Eg. player, team, season, etc. You would have :player/id , :team/id, :season/id instead of :player-id, :team-id, :season-id, and such.

And definitely not the horror of:

{:player {:id 42}, :team {:id 11}, :season {:id 99}}

In general, the situation where I find them the most useful is when the map is a "bag" of fields from different entities that are all combined together for convenience or correlation (data that has be joined.)

You can do nifty stuff like this:

(merge
  (select-keys player [:player/id :player/name])
  (select-keys team [:team/id :team/name])
  (select-keys season [:season/id :season/year :season/phase]))

So that would be an expanded record of information about a player that would include more context: the team the player was on (at the time) and the related season.

@leif.eric.fredheim Let me know if that's helpful!

https://clojurians.slack.com/archives/CKKPVDX53/p1571062159004200

Jump to that message and look at the thread and other messages in the channel after.

Here is Christoph with an example: https://clojurians.slack.com/archives/CKKPVDX53/p1571075516008300

Here's a mention of a Stuart Halloway talk: https://clojurians.slack.com/archives/CKKPVDX53/p1571110664017800

I believe we also talk about namespacing keys in our Maps! Maps! Maps! episode: https://clojuredesign.club/episode/051-maps-maps-maps/

@neumann Why is the nested data horrible though?