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
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
Apparently there's a problem with the Plunker API that "doesn't take module names
into account". I'm not entirely certain what the exact problem is, or if there's a way to build the example that works around it; see this discussion for a little more info: https://groups.google.com/forum/?fromgroups=#!topic/angular/ng6LGzr53po
Of course if there's an issue with that external API, it would need to be fixed there, if it can't be worked around.
The code example uses HTML5 router mode, arguably best practice, but it requires server setup that Plunker/JSFiddle won't have. Suggest a simple note to that effect next to the sample, describing the (hopefully simple) changes needed to work on the sharing sites.
The text was updated successfully, but these errors were encountered:
Secondly, the plunkr seems to work just fine now. I followed the link to the google group discussion, but it doesn't really say they changed anything, so I'm not sure why it works now. Perhaps the example changed? So I think both of your bullet points above have been taken care of at this point.
I can't close this issue, so just reporting my findings. Please close if you can confirm.
Thnx @sirkitree, I've just tested both plunker and jsFiddle and indeed things are in order now. AFAIK the original problem was that not all the required files were correctly included in generated plunks / fiddles.
Ex: http://docs.angularjs.org/api/ng.directive:ngView
There are two issues there:
into account". I'm not entirely certain what the exact problem is, or if there's a way to build the example that works around it; see this discussion for a little more info:
https://groups.google.com/forum/?fromgroups=#!topic/angular/ng6LGzr53po
Of course if there's an issue with that external API, it would need to be fixed there, if it can't be worked around.
The text was updated successfully, but these errors were encountered: