We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
window.history
Hi, Either I've miss something or not, but the README doesn't make any mention of window.history
I was trying to test my back button that basically does window.history.back() but my test was still returning to the previous page 😅
window.history.back()
In the controller that contain the goBack function I've added import window from 'ember-window-mock';
goBack
import window from 'ember-window-mock';
and in the test I've added both import { setupWindowMock } from 'ember-window-mock'; and setupWindowMock(hooks);
import { setupWindowMock } from 'ember-window-mock';
setupWindowMock(hooks);
Is this out of scope to support things like that with history or should I do it another way ?
history
Thanks for your help
The text was updated successfully, but these errors were encountered:
It is basically a missing feature! 🙂
Keeping this here as a feature request. But not sure if I am able to implement this in the foreseeable future. PRs certainly welcome...
Sorry, something went wrong.
No branches or pull requests
Hi,
Either I've miss something or not, but the README doesn't make any mention of
window.history
I was trying to test my back button that basically does
window.history.back()
but my test was still returning to the previous page 😅In the controller that contain the
goBack
function I've addedimport window from 'ember-window-mock';
and in the test I've added both
import { setupWindowMock } from 'ember-window-mock';
and
setupWindowMock(hooks);
Is this out of scope to support things like that with
history
or should I do it another way ?Thanks for your help
The text was updated successfully, but these errors were encountered: