Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/reference/gridfs/#the-files-collection
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2453.0 Safari/537.36
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: reference/gridfs
Description
I've just chased down some big challenges with Meteor File Collection which uses GridFS. Turns out that both the author and I didn't realize that arbitrary data could be added at the top level of the schema. I later spotted that fact in your earlier text, but perhaps the following change in the metadata description will help Devs spot this capability a bit better:
Recommend Changing:
files.metadata
Optional. Any additional information you want to store.
To:
files.metadata
Optional. Any additional information you want to store. Though you may also create your own arbitrary fields at the level above this.