Provide XML schema for angular directives, widgets

[vojtajina]

So that we can enable validation and completion of angular tags.
This schema could be generated during docs build.
And should be published on http://angularjs.org/

Note:
As htmlř doesn't use xml namespaces (xmlns:ng="http://..."), we should try it at first - generate the schema for one directive and test it with some IDEs...

Something about xmlschema: http://www.w3schools.com/schema/
Related mailing list topic: https://groups.google.com/forum/#!topic/angular/MtMysRKFveQ

[mansona]

Is there any part of the documentation that has the full list of ng: namespace tags?

[LeDominik]

This would be pretty cool to enable all kinds of auto-completion in advanced IDE's like Eclipse, IDEA, etc... It works very nicely already for plain HTML when including the xmlns= tag following the W3C standard: http://dev.w3.org/html5/spec/Overview.html#namespaces

[mindplay-dk]

Having Angular's attributes actually namespaced as "ng:", rather than prefixed with "ng-", would have been helpful - for validation as well as for IDEs, and to avoid ambiguity in general.

It's too bad, it doesn't look like this feature is going to make it into release 1.0 - and I'm afraid that this will most likely never happen now, since it isn't happening prior to 1.0, as it would break backwards compatibility.

It gets particularly bad when you start adding custom tags (components) as these are just basically plain invalid markup, which will cause all your documents to fail validation.

In my opinion, this is a pretty big oversight and something that should have been rectified prior to official 1.0 release...

[mhevery]

we support ng:dir as well as ng-dir, so shouldn't this be sufficient for IDEs?

[mindplay-dk]

I didn't know that, but I wonder why you promote the use of the prefix rather than the namespace? Seems like you're teaching bad habits.

Is it possible to namespace component tags, too?

Is there a schema that would provide for validation?

[mindplay-dk]

I tried namespacing the component-tags in one of the samples, and it does not work:

http://jsfiddle.net/mindplay/PsnM9/2/

If this worked, we could actually namespace modules within an application - for example, you could namespace components from a common ui-library as "ui:" and application-specific components as "app:"...

[mhevery]

It works just fine: http://jsfiddle.net/PsnM9/3/

[mindplay-dk]

Ah, I see - the namespace portion of the directive-name gets normalized, too!

The directive page in the guide isn't really clear on what precisely normalization means, and very few (if any?) of the examples actually use namespaced XML directives.

[fitzchak]

Looking for this schema too in order have Visual Studio intellisense working with AngularJS!

[ebeltran1981]

I will love to have this :) 👍

_e

[bkbonner]

Any word on this?

[ebeltran1981]

Per my research, the AngularJS team is not planning to support this.

I made my own solution using plain JS and jQuery.

Regards,

Edwin Beltrán
Sent from my iPhone 4S.

On Oct 30, 2012, at 5:30 PM, bkbonner notifications@github.com wrote:

Any word on this?

—
Reply to this email directly or view it on GitHub.

[bkbonner]

Thank you. I was thinking about using this approach the XHTML schema to work with Angular's NG namespace: http://www.w3.org/TR/xhtml-modularization/schema_developing.html