Skip to content

Leverage Arrow functions. Browser history nav button issue #5606

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

Merged
merged 3 commits into from
Apr 22, 2020
Merged

Leverage Arrow functions. Browser history nav button issue #5606

merged 3 commits into from
Apr 22, 2020

Conversation

holylander
Copy link
Contributor

Category

  • Content fix
  • New article

Related issues:

What's in this Pull Request?

I have proposed these changes beacuse:

  • When trying to leverage this on my spfx extension, using yeoman, I had issues on the code and the solution was to implement arrow functions. Also, it makes the code more understable.
  • I have noticed that when using the back/forwards browser history buttons, doesnt have any effect, when the conditionally page load is in place ( aka page transition ). For instance, you can go to a library, and start to browser among the folders. You will notice that clicking on back/forward doesnt have any effect on page content load.
  • I have documented how you can pass the url info change to the event handler
  • This approach can help users to track down which folder the user is browsing, on a list/library

I have proposed these changes beacuse: 
- When trying to leverage this on my spfx extension, using yeoman, I had issues on the code and the solution was to implement arrow functions. Also, it makes the code more understable.
- I have noticed that when using the back/forwards browser history buttons, doesnt have any effect, when the conditionally page load is in place ( aka page transition ). For instance, you can go to a library, and start to browser among the folders. You will notice that clicking on back/forward doesnt have any effect on page content load.
- I have documented how you can pass the url info change to the event handler
@msftclas
Copy link

msftclas commented Apr 19, 2020

CLA assistant check
All CLA requirements met.

Also replaced `query`per `search`. url.query property returns nothing nowdays.
Copy link
Contributor Author

@holylander holylander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some extra changes added to my previous pull request

Updated timestamp on file (`ms.date` front matter property) and fixed code formatting issues.
@andrewconnell andrewconnell merged commit 9f7603c into SharePoint:master Apr 22, 2020
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.

3 participants