Skip to content
New issue

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

Resolve triggering twice #3833

Open
3 of 6 tasks
daniklein30 opened this issue Aug 15, 2021 · 1 comment
Open
3 of 6 tasks

Resolve triggering twice #3833

daniklein30 opened this issue Aug 15, 2021 · 1 comment
Labels

Comments

@daniklein30
Copy link

daniklein30 commented Aug 15, 2021

This issue tracker is for Bug Reports and Feature Requests only.

Please direct requests for help to StackOverflow.
See http://bit.ly/UIR-SOF for details.

This is a (check one box):

  • Bug Report
  • Feature Request
  • General Query

My version of UI-Router is: (type version) - 0.3.2

Bug Report

Current Behavior:

New URL entered into the browser for the first time triggers resolve twice

Expected Behavior:

To only trigger once

Link to Plunker or stackblitz that reproduces the issue:

Its a massive application without the ability to isolate and make a Plunker out of it
( if you want a response to your issue, provide a way to reproduce it )
( http://bit.ly/UIR-Plunk1 )
( https://stackblitz.com/edit/ui-router-angularjs )

Feature Request

(type feature request here)

General Query

Please direct general implementation questions to StackOverflow:
http://stackoverflow.com/questions/ask?tags=angularjs,angular-ui-router

Please review the Sample Application which highlights common approaches:
https://github.com/ui-router/sample-app-angularjs

  • I have already asked my question on StackOverflow and nobody could answer the question

  • I have already reviewed the sample application for examples of common approaches

  • I believe my question can only be answered by the UI-Router maintainers

(type general query here)

@stale
Copy link

stale bot commented Apr 18, 2022

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs.

This does not mean that the issue is invalid. Valid issues
may be reopened.

Thank you for your contributions.

@stale stale bot added the stale label Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant