DURL keeps your i-frame's Deep URL stored in the hash fragment of your parent page
Stars
2
Forks
2
Watchers
2
Open Issues
0
Overall repository health assessment
^1.0.3^3.4.1^3.9.0^2.2.0^2.3.423
commits
Do not strip 2nd query params onwards from vanillaHash
b355f91View on GitHubfixed a bug if consumer has a <base href=...> set, see comments
d285ac4View on GitHubI feel like this comment is better suited for the setDURL method
3dcc6ddView on GitHubupdated comments to include version # in durl.js, so that duel-rails gem can compare itself against its vendored copy
42756b8View on GitHubbad merge, this was supposed to be removed in 6d9ca278
a15ba4cView on GitHubso the last fix was in error, we don't always need to decode the path here because it's already decoded on the other side. However, due to some bugs in the react-router (v 0.11.6), it ends up double-encoding the DURL on its side. So we decode it twice in this case, at least for now :(
6d9ca27View on GitHubpath should be decoded in setDurlFromConsumer. Relative paths were failing to make page navigate because window.location.replace was receiving an encoded leading / instead of a real one.
fd9d860View on GitHub