set history to true by default to improve developer experience. #2434
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It took a while to understand why I had to start from the beginning for every change. Searching for that is not easy either.
See issue #2175
While I am developing a presentation, I would like to stay on the current working slide. But after saving changes page is reloaded and presentation is moved to the first slide. It is very annoying. Is there any way to force reveal.js to stay on the current working slide during development? Thanks.
possible improvement: add a npm command such as
npm dev
which will automatically set history to true without writing it inside the reveal.js Init function.