model json file bug

[oderayi]

Great tool!

I observe that the generated model json files have "settings" attribute instead of "options" attribute.

{ "name": "Customer", "properties": { ... }, "settings": { "strict": false, "forceId": false, "replaceOnPUT": true, "idInjection": false, "mysql": { "schema": "my_store", "table": "customer" } } }

I think "settings" should be "options" at least for the version of loopback I'm using (v3).

[akera-io]

Thanks for your comment, I'll give V3 a try and see what can be done... as far as I can see the json model definition still uses 'options', no mention of 'settings' there - https://loopback.io/doc/en/lb3/Model-definition-JSON-file.html

[akera-io]

Could you let me know what connector are you using? We're not altering the model definition when saving it, maybe the database connector uses 'settings' instead of 'options' in discovered models. Guess we can try to see if options are missing and then look for settings or anything like that, it might be easier to just fix the discovery part in that connector you're using though.

[oderayi]

Thanks @akera-io. I am using the mysql connector.
To clarify, I am getting "settings" in my discovered model json files rather than "options" which is the correct name for V3. So I had to manually change all "settings" to "options" in my model json files.