Skip to content

Commit d022f47

Browse files
committed
Change the link to something actually working
1 parent 8065653 commit d022f47

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

documentation/extending.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ with the path to the current form field on the model, i.e. `form.key`.
187187
So `ng-model="$$value$$"` becomes something like `ng-model="model['person']['address']['street']"`,
188188
you can see this if you inspect the final form in the browser.
189189

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.*
191191

192192
So basically, you always have a `ng-model="$$value$$"` (Pro tip: ng-model is fine on any element, put
193193
it on the same div as your custom directive and require the ngModelController for full control).

0 commit comments

Comments
 (0)