right now I have this form:
When you use ng-model
it is to bind your form components to the scope using certain name. this means that
<input ng-model="stickie_text" type="text" id="sticky_content" />
will bring you a $scope.stickie_text
with the current value of your component in your 'formCtrl'
controller. Remember it's a bidirectional binding: if you alter that variable, you also alter the value in the form control.
Let's refactor this:
<form ng-submit="submit()" ng-controller="formCtrl">
<input ng-model="stickie_text" type="text" id="sticky_content" />
<button type="submit" id="add_sticky" value="add a new stickie!">new sticky</button>
</form>
This form has only one field: stickie_text
. The other one is a button.
So far, your form has one field, which stores and reads data in the scope in the specified name ($scope.stickie_text
).
When you submit the form, your $scope.submit
function is being invoked:
$scope.submit = function() {
$http
.post('/api/stickies', {what: to, put: here})
.success(function(data){
//what to do here
})
.error(function(data){
console.log('Error: ' + data);
});
};
So this is your handler and the big question is:
Notice I changed your handler a bit - placing a comment and replacing the data object.
The POST data must match the server-side. So if your stickie must fly through the network under the name stickie
(in this way, a req.body.stickie
expression exists on the server-side), the data you must compose is this: {stickie: $scope.stickie_text}
. This is because stickie_text
is the name you used in the view, and so it's the name of the scope var where such field will read and write from. Remember to install the body parser
middleware in your application.
I don't remember much of nodejs, but if I'm right, perhaps doing:
app.post('/api/stickies',function(req,res){
var test = req.body.stickie;
db.run("INSERT INTO stickies (data) VALUES (?)", [ test ]);
});
Will do it AS LONG AS YOU USE THE SAME DATA KEYS FROM THE CLIENT. You should also write something in the response (res
) object, but that's up to you and nodejs, and your preferred way (e.g. res.write
).
So, we'll stick to the same example:
$scope.submit = function() {
$http
.post('/api/stickies', {stickie: $scope.stickie_text})
.success(function(data){
//what to do here? it's up to you and the data you write from server.
})
.error(function(data){
console.log('Error: ' + data);
});
};
Test this, and check your database.
Edit - suggested by @Kousha - Use a de-facto namespace for your form data (as you said formData
beforehand - remember this is an example and you can use any name you want). It works like this:
Give a prefix to each of your fields in the ng-model
, so the same object holds the form data. Since you have only ONE field, it will be enough:
ng-model="formData.stickie"
deliberately I changed the variable name to match the name waiting in the nodejs server. Don't forget this, since I'll use the object directly as data.
The final value of $scope.formData
will be {stickie: whatEverIsInTheInputField}
. If I added another field using ng-model="formDta.foo"
as binding, the final value of $scope.formData
would be {stickie: whatEverIsInTheInputField, foo: otherFieldValue}
.
I use the $scope.formData
directly in the http request:
$scope.submit = function() {
$http
.post('/api/stickies', $scope.formData)
.success(function(data){
//what to do here? it's up to you and the data you write from server.
})
.error(function(data){
console.log('Error: ' + data);
});
};
Although formData
did not exist in the $scope
beforehand, the binding created it implicitly before creating stickie
under it.