models
Here are 60 public repositories matching this topic...
-
Updated
Jul 14, 2020 - JavaScript
This is a forum to discuss support and implementation of Joi extensions.
In order to maintain a 1:1 api parity with Joi, we will eventually need some level of support for Joi extensions.
It's important to note in thinking about implementation that extensions do not modify the Joi module itself, but provide a new Joi instanc
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
May 15, 2020 - JavaScript
-
Updated
May 2, 2019 - JavaScript
Right now the result of sequelize-auto-import is an object that will have its properties equal to the model name of the meta object that we pass to each model, but practically the dev can choose to not use these values an put other values for the model name and schema so we must extract these values from the sequelize model instead.
-
Updated
Jun 10, 2020 - JavaScript
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
Jan 20, 2019 - JavaScript
-
Updated
Oct 2, 2019 - JavaScript
-
Updated
Jun 2, 2020 - JavaScript
-
Updated
Nov 29, 2019 - JavaScript
-
Updated
Feb 19, 2017 - JavaScript
-
Updated
Jun 7, 2020 - JavaScript
-
Updated
Mar 1, 2018 - JavaScript
-
Updated
Apr 21, 2017 - JavaScript
-
Updated
Jun 1, 2020 - JavaScript
Improve this page
Add a description, image, and links to the models topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the models topic, visit your repo's landing page and select "manage topics."
I'm trying to find out how to fit vue-mc into my app's architecture, and the docs are helpful, but maybe I am missing something obvious:
In the Vue docs data section, it reads:
Where should I store my model instance otherwise?