You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the implementation for Waterline as our default model system we add amazing features, for example: simplification on the model declaration, support for multiple types of databases, the creation of new a record is easier than before, and so on. But we also lose some features as the inner population or populate after a method or have a method to update just one record and get just one object as the returned value, and not an array.
So we need to make a fork of the current model system (Waterline) to address this issues and implement this required features that all of us need. This will be a long journey and we will need all the help you can give in order to move forward.
For now we will discuses and describe the features as better as possible, after that we will create a issue for each feature to better track the work we need to do and what we have done.
Please, comment and give some suggestion to append to the list below.
List of features to implement
populate after an update
whenever the first parameter of update method is an ID (string or number) the return must be the updated object and not an array
For Mongo
a way to define a $text index (balderdashy/sails-mongo#357)
The text was updated successfully, but these errors were encountered:
With the implementation for Waterline as our default model system we add amazing features, for example: simplification on the model declaration, support for multiple types of databases, the creation of new a record is easier than before, and so on. But we also lose some features as the inner population or populate after a method or have a method to update just one record and get just one object as the returned value, and not an array.
So we need to make a fork of the current model system (Waterline) to address this issues and implement this required features that all of us need. This will be a long journey and we will need all the help you can give in order to move forward.
For now we will discuses and describe the features as better as possible, after that we will create a issue for each feature to better track the work we need to do and what we have done.
Please, comment and give some suggestion to append to the list below.
List of features to implement
update
method is an ID (string
ornumber
) the return must be the updated object and not an arrayFor Mongo
$text
index (balderdashy/sails-mongo#357)The text was updated successfully, but these errors were encountered: