New type: ENUM

[bajtos]

Implement a new property type - enum (enumeration).

Example model definition:

{
  "name": "Person",
  "properties": {
    "sex": {
      "type": "enum",
      "values": ["male", "female", "other"]
    }
  }
}

Example remoting argument definition:

{
  accepts: { 
    arg: 'sex', type: 'enum', values: ['male', 'female', 'other'],
    http: { source: 'query' }
  }
}

Implementation details:

• support both "string" and "number" as a backing datatype
• strong-remoting should validate and coerce enumeration types
• loopback-datasource-juggler should validate property values of enum type
• connectors should map enum type to appropriate database counterpart
  • SQL connectors - see https://github.com/strongloop-internal/scrum-loopback/issues/603
  • MongoDB - see https://github.com/strongloop-internal/scrum-loopback/issues/604
• loopback-swagger should emit correct json-schema descriptor for enum properties
• autodiscovery

[raymondfeng]

Instead of introducing a new type, I would prefer to add a enum constraint to model properties, such as:

color: {
  type: 'string',
  enum: ['red', 'green', 'blue', ...]
}

It's similar as https://github.com/hapijs/joi#anyvalidvalue---aliases-only-equal

[bajtos]

Instead of introducing a new type, I would prefer to add a enum constraint to model properties

Sounds good 👍

[violet-day]

+1

[bajtos]

FWIW, we already have ENUM validation implemented via MyModel.validatesInclusionOf('gender', {in: ['male', 'female', 'other']});

I guess we only need to map enum property flag to validatesInclusionOf and implement support for enum in strong-remoting.

[ainesophaur]

+1

Would these additions then translate to loopback explorer? It'd be nice to show the allowed values.

[billinghamj]

+1

[gausie]

👍

[Bramanga]

👍

[ezraroi]

+1

[MyNameIsURL]

+1

[terehov]

+1

[parvbhullar]

+1

[sudomf]

+1