GeoJSON type about mongoose-geojson-schema HOT 5 CLOSED

I see what you mean. I'm not sure what risk there is of collisions now, but certainly using GeoJSON as the top-level Schema element would be very-low risk.

If you wanted to go ahead and refactor a 2.0 release soon, I doubt many people have had a chance to adopt the 1.0.x syntax.

As long the amount of syntax people need is similar and we get clear diagnostic messages, I'm in favor of the change.

from mongoose-geojson-schema.

Yes, I'll see what I can do. I don't foresee a major change in the codebase to implement this.

from mongoose-geojson-schema.

Done. v2.0.0 is out.

from mongoose-geojson-schema.

From the README, it appears the validation just got weaker. Here's an example of the new syntax:

  point: mongoose.Schema.Types.GeoJSON,

Before, a point could be validated as a GeoJSON Point. Is the new syntax looks like it would allow /any/ valid GeoJSON object to be used where only a point was expected. Is that the case?

I was expecting a syntax more like one of these:

 point: mongoose.Schema.Types.GeoJSON.Point,
// OR
 point: mongoose.Schema.Types.GeoJSON({ type: Point })

In 2.0, how would specify that I wanted a field to be validated as GeoJSON Point?

from mongoose-geojson-schema.

@markstos You're absolutely right. Too tired to notice that glaring omission.

Mongoose doesn't allow nested schemas, so I've readded the v1.0 types to the Types. I've kept the GeoJSON type in case anyone wants to be flexible about the type they're using.

from mongoose-geojson-schema.