API v2 feedback: files' ".tag" attribute extremely unfriendly for HTTP/JSON

Thanks for the feedback! I think you're specifically talking about JavaScript, right?

The dot wasn't meant to indicate that the field is private–clients definitely need to read it. It was meant to be in a namespace that would never cause collisions. A dot seemed like a good way to do that, since it's uncommonly used in a JSON dictionary key.

It's unfortunately too late to change this for API v2, which just recently came out of beta. But we could consider changing it in a future version of the API. I'd love to hear specific examples ofwhere this causes trouble, e.g. in lodash.

This seems to work fine:

var files = _.filter(entries, '.tag', 'file');