And if you don't see a test for something you spotted, feel free to make an issue. Check the project board for open tickets to work on. These are relatively easy to do, and a fantastic way of getting introduced to the wonders of BookReader. We write tests for the repo itself and also for our use on. We also have end to end tests using Testcafe. We would like to get to 100% test coverage and are tracking our progress in this project: BookReader Fidelity End to end tests We release BookReader in-repo as tags & also as a node module Tests It'll automatically update the version number where it appears, build the files, and ask you to update the CHANGELOG. To version bump the repo and prepare a release, run npm version major|minor|patch (following semver), then (something like) git push origin HEAD -tags. You may now start a local server to see your changes by running command: npm run serve-dev.Navigate to /bookreader and run command: npm link You can use the command npm ls |grep icon-share to confirm icon-share is now a link to your local directory.You can use the command npm ls -g to confirm your local package now appears in the registry.From within your icon package directory run command: npm link.You shouldn't need to commit any of these core-js changes.Navigate to your icon package ( iaux-icons/packages/icon-share) and run command: npm install core-js.Confirm your icon package is working properly in the iaux-icons demo.To see local icon package changes in bookreader, you'll need to install core-js into the icon package and link into bookreader. Anything in the BookReader/ directory should not be committed. Please DO NOT include these files in your PR. Until the next major version bump, we have to store the build files inside the repo to maintain backwards compatibility. npm run serve-dev starts an auto-reloading dev server, that builds js/css that has been edited at localhost:8000. The source JavaScript is written in ES6 (located in the src/js directory) and in ES5 (located in BookReader). The “fragment” is formatted in accordance with the BookReader URL spec. When the receives this message, it moves to the specified page/mode. The Fragment Change message is sent to the parent window when the embedded BookReader moves between pages/modes. The parent window can send messages of its own (also via window.postMessage()) and the IFrame Plugin will handle updating the reader to match. If you use the IFrame Plugin inside the, the reader will send notifications about changes in the state of the reader via window.postMessage().
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |