- 08 Mar, 2017 8 commits
-
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
config.md was interchangeably using "sidebar" and "client" to refer to the client. Fix it to always use "client" because it's more consistent. I chose client instead of sidebar because (both technically speaking and in terms of the UI) not all of these settings actually refer to the sidebar, e.g. showHighlights and assetRoot. Also client is the word used by the git repo name and in the README file.
-
Sean Hammond authored
For example "Client behavior" was a sibling heading of "Config keys", not a sub heading as intended. Fix all the heading levels so that headings are nested as they were intended to be.
-
Robert Knight authored
Add overview of client security considerations
-
Nick Stenning authored
Add a preliminary overview of client security considerations and implementation decisions.
-
- 06 Mar, 2017 11 commits
-
-
Robert Knight authored
Developing docs tweaks
-
Sean Hammond authored
-
Sean Hammond authored
sudo isn't required on all systems (e.g. macos)
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
-
Sean Hammond authored
For example Node is a prerequisite because we just tell you that you're going to need it before you can follow these instructions. Gulp is not a prerequisite, it's a dependency, because the instructions tell you how to install it.
-
Sean Hammond authored
-
- 03 Mar, 2017 1 commit
-
-
Robert Knight authored
This OS-specific dependency was inadvertently added to the shrinkwrap in ed4afca0
-
- 02 Mar, 2017 3 commits
-
-
Sean Roberts authored
Add eslint rule to raise a warning if any of the tests are using the …
-
Sean Roberts authored
Add a guide to developing the Hypothesis client
-
Sheetal Umesh Kumar authored
-
- 01 Mar, 2017 11 commits
-
-
Robert Knight authored
-
Robert Knight authored
Add an initial guide to developing the Hypothesis client, covering: - Installation - Getting a local build of the client working with the browser extension or a local Hypothesis service - Running tests - Some basic pointers on code style and where to find guidance for creating pull requests This guide assumes that the service is configured to use the client's new boot script.
-
Robert Knight authored
Add tests for login control.
-
Sheetal Umesh Kumar authored
-
Robert Knight authored
Add CORS headers to assets served by the client's dev server, otherwise the client's icon font will fail to load in many browsers.
-
Robert Knight authored
-
Robert Knight authored
Due to a problem where an earlier version of 1.0.0 and 1.1.0 were published to npm and then unpublished, thereby preventing re-use of these versions, we're going to skip straight to 1.2.0.
-
Robert Knight authored
-
Robert Knight authored
-
Robert Knight authored
-
Robert Knight authored
Call partner provided login callback
-
- 28 Feb, 2017 5 commits
-
-
Robert Knight authored
An inconsistency crept in where the annotator code reads settings from JSON script tags with a 'js-hypothesis-config' class name but the sidebar app reads settings from JSON script tags with a 'js-hypothesis-settings' class name. The boot script ended up using 'js-hypothesis-settings' which is the default class name specified in `settings.js`. We should use the same name everywhere, which needs to be 'js-hypothesis-config' since that is used by the public documentation [1]. This commit changes the default class to `js-hypothesis-config` and removes the ability to specify alternative class names when calling `settings()`. The extension and service will need to be updated to use the new class name. [1] See docs/config.md
-
Nick Stenning authored
Add an express server which serves the package's contents.
-
Sean Hammond authored
Fix PDF quote anchoring (Part II)
-
Sean Hammond authored
When the client is embedded in a partner site and a login button in the client is clicked, call the JavaScript onLogin function that was provided to us by the partner via the window.hypothesisConfig function. When not embedded in a partner site, just prompt for a first-party login as normal. Note that this means that if the client is embedded in a partner site with no onLogin callback in window.hypothesisConfig, then nothing will happen when the login button in the client is clicked.
-
Sean Hammond authored
Separate bridge events sent from sidebar to annotator and from annotator to sidebar into two separate sections in the source code. Just to make documentation of the events clearer.
-
- 27 Feb, 2017 1 commit
-
-
Robert Knight authored
- /hypothesis and /hypothesis@X.Y.Z serve the boot script - /hypothesis/X.Y.Z/ serves the files for a given version of the package
-