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

Adding support for hash linked slideNumber #2133

Merged
merged 3 commits into from
Apr 16, 2018
Merged

Adding support for hash linked slideNumber #2133

merged 3 commits into from
Apr 16, 2018

Conversation

sean-parent
Copy link
Contributor

There are two changes here -

Make the hash slide numbering match the shown slide so that slide.html#/3 is slide 3 and not slide 2.

Added an href link to the slide number if shown to make it simple to share a link to a particular slide even when history is not enabled. This also makes it easy to lock to a particular slide when using auto refresh tools while developing.

@mschilli87
Copy link

This was suggested before but decided against: #2067

@sean-parent
Copy link
Contributor Author

Recommendations to proceed?
I could make 1 based hash indexing optional
I could drop 1 based hash indexing and just keep the href link in the slide number
I could make the href link in the slide number optional
Other suggestions?

@hakimel
Copy link
Owner

hakimel commented Mar 23, 2018

I think it'd be best to make the 1-based indexing optional to avoid breaking existing content. If you can revise that I'd be happy to merge this in. Thanks!

@sean-parent
Copy link
Contributor Author

One based indexing is now optional (defaults to zero based for compatibility)

@hakimel
Copy link
Owner

hakimel commented Mar 27, 2018

Thanks for updating. One more thing, can you change the merge target of the PR to the 'dev' branch? That's the working branch, we merge dev into master when a new version goes out.

@marcosalpereira
Copy link

There is still something preventing the incorporation of this change?

@mschilli87
Copy link

@hakimel: If it's just the wrong target branch, you should be able to change that yourself:
https://blog.github.com/2016-08-15-change-the-base-branch-of-a-pull-request/

@sean-parent sean-parent changed the base branch from master to dev April 13, 2018 14:44
@sean-parent
Copy link
Contributor Author

Merged to dev branch and resolved conflicts.

@hakimel hakimel merged commit f713d9d into hakimel:dev Apr 16, 2018
@hakimel
Copy link
Owner

hakimel commented Apr 16, 2018

Thanks for resolving the conflicts 🙌

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.

None yet

4 participants