Skip to content

fix (UDM): fixing broken path to rangy#1200

Open
morficus wants to merge 1 commit intotextAngular:masterfrom
morficus:rangy-fix
Open

fix (UDM): fixing broken path to rangy#1200
morficus wants to merge 1 commit intotextAngular:masterfrom
morficus:rangy-fix

Conversation

@morficus
Copy link
Copy Markdown

@morficus morficus commented Jun 3, 2016

Correcting the path used in the UMD module for loading rangy via AMD loaders to account for the "rangy" vs "rangy-release" discrepancy.

closes #1199

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 0e29bfc on morficus:rangy-fix into fe544a6 on fraywing:master.

Correcting the path used in the UMD module for loading rangy via AMD loaders to account for the "rangy" vs "rangy-release" discrepancy.

closes textAngular#1199
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling ab4b711 on morficus:rangy-fix into fe544a6 on fraywing:master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rangy fails to load via UMD when using Bower

2 participants