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
Contact @davidlgj or @Anthropic to ensure you don't work on something already in progress!
6
+
7
+
A few things to note:
8
+
* Error messages are not handled in the standard Angular Material way due to ASF behaviour.
9
+
To add messages to a template add **sf-messages** to the **parent** you want messages to be the last child of.
10
+
* Look at the API page for the Angular Material component you are looking at, there are possibly a few attributes
11
+
not used in the demo that may be useful. Please try to add as many useful attributes as you can, we can discuss the
12
+
best way to implement them in the ASF form data.
13
+
14
+
As an example, if the template requires a remote titleMap, consider adding optionData as a variable in the form definition that can contain a text string reference to a variable on the sf-form $scope.
15
+
16
+
**Please base any merge request on the *development* branch instead of *master*.**
17
+
18
+
The reason for this is that we're only really using *development* for now but will eventually start trying to use
19
+
[git flow](http://danielkummer.github.io/git-flow-cheatsheet/), and it makes merging your pull
20
+
request a heck of a lot easier for us.
21
+
22
+
Please **avoid including the material-decorator.js or material-decorator.min.js** as that can make merging harder, and we
23
+
will always generate these files when we make a new release.
24
+
25
+
With new features we love to see updates to the docs as well as tests, that makes it super
26
+
easy and fast for us to merge it!
27
+
28
+
Also consider running any code through the **JavaScript Code Style** checker [jscs](https://github.com/mdevils/node-jscs)
29
+
(or even better use it in your editor) using the .jscsrc file in the repo root, which should be picked up by the IDE. You can also us `gulp jscs` to
Copy file name to clipboardExpand all lines: README.md
+36-6Lines changed: 36 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,18 @@
1
1
Angular Material Decorator
2
2
==========================
3
3
4
-
For https://github.com/Textalk/angular-schema-form
4
+
[](https://gitter.im/json-schema-form/angular-schema-form-material?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
5
5
6
+
For https://github.com/json-schema-form/angular-schema-form
6
7
7
-
Very very very much work in progress.
8
+
Work In Progress
9
+
----------------
10
+
As Angular Material has not reached 1.0.0 yet, this decorator is progressing very cautiously until that project hits it's stable milestone.
8
11
12
+
Meaning that it is **very** much a **work in progress**.
13
+
14
+
Testing
15
+
------------
9
16
To test clone repo and:
10
17
```
11
18
npm install
@@ -20,7 +27,30 @@ There is also a `gulp watch` task that minifys on change.
20
27
21
28
Known Issues
22
29
------------
23
-
* Almost nothing work
24
-
* Only inputs and textare are implemented
25
-
* No angular material "theme". Looks like an issue with us using $compile in the link function of
26
-
our directives.
30
+
* Almost nothing works if the schema uses bootstrap decorator features, it does not have array or complex keys yet and many other features are still missing or have no equivalent.
31
+
* Needs development branch of angular schema form.
32
+
* Only basic support for inputs, textarea, radios, radiobuttons, checkboxes, datepicker and tabs are implemented.
33
+
* Angular material theme only works when `$mdThemingProvider.alwaysWatchTheme(true);` is used.
34
+
* Until Angular Material hits 1.0.0 there is still chances that features may break again.
35
+
36
+
Contributing
37
+
------------
38
+
Contributions are welcome! Please see [Contributing.md](CONTRIBUTING.md) for more info.
39
+
40
+
Future
41
+
------
42
+
Using the new builder opens up for a lot of optimization. Primarily we can get rid of a lot of small
43
+
watches by using build helpers. For instance, slapping on a `sf-changed` directive *only* if the
44
+
form definition has an `onChange` option.
45
+
46
+
47
+
Testing
48
+
-------
49
+
```
50
+
npm install -g protractor
51
+
protractor test/protractor/conf.js
52
+
```
53
+
54
+
change baseurl in test/protractor/conf.js to match ur local environment.
55
+
56
+
Copyright (c) 2016 Marcel John Bennett, David Jensen
0 commit comments