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
Copy file name to clipboardExpand all lines: documentation/extending.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -187,7 +187,7 @@ with the path to the current form field on the model, i.e. `form.key`.
187
187
So `ng-model="$$value$$"` becomes something like `ng-model="model['person']['address']['street']"`,
188
188
you can see this if you inspect the final form in the browser.
189
189
190
-
*Hint: The [camelCase example](https://github.com/OptimalBPM/angular-schema-form-add-ons/tree/master/examples/camelcase) actually prints out the value of $$value$$ in the second field.*
190
+
*Hint: The [camelCase example demo](http://demo.optimalbpm.se/angular-schema-form-add-ons/examples/camelcase/example.html) actually prints out the value of $$value$$ in the second field.*
191
191
192
192
So basically, you always have a `ng-model="$$value$$"` (Pro tip: ng-model is fine on any element, put
193
193
it on the same div as your custom directive and require the ngModelController for full control).
0 commit comments