playframework / playframework/playframework
Evolutions URL generation does not work well with Hashtag URLs
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 12.6k
- Forks
- 4k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 29
Description
Are you looking for help?
Hello, currently we are using Play with AngularJS and his Hashtag Router.
Currently if we change a evolution and refresh the browser while still having a url like localhost:9000/#/home it can't apply the evolution since the redirect link to apply them is broken.
Actually I think that only happens when not using the autocommit mode and getting the javascript location.replace url. (i.e. on play-slick)
Play Version (2.5.x / etc)
2.5.x only
API (Scala / Java / Neither / Both)
Scala
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Play 2.5.x with the Scala API, AngularJS hashtag routing, and a URL such as localhost:9000/#/home. Compare evolution changes with autocommit disabled, especially the javascript location.replace redirect; done means the evolution can be applied after refreshing a hashtag URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, scala
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100