This example shows you how to use selenium-webdriver and selenium-standalone in modern versions with Firefox, Chrome and Safari and without the promise manager.
angular.module('extensions.restangular.auto-update', [ | |
'restangular' | |
]); | |
angular.module('extensions.restangular.auto-update') | |
.factory('RestangularAutoUpdate', function RestangularAutoUpdate(Restangular) { | |
// properties | |
var _routes = []; |
import React from 'react'; | |
import expect from 'expect'; | |
import ReactTestUtils from 'react-addons-test-utils'; | |
export const NameComponent = ({ name }) => <span>Hello {name}!</span>; | |
describe('name component', () => { | |
it('should render the name', () => { | |
const renderer = ReactTestUtils.createRenderer(); | |
renderer.render(<NameComponent name="foo" />); |
import React from 'react'; | |
import expect from 'expect'; | |
import { shallow } from 'enzyme'; | |
export const NameComponent = ({ name }) => <span>Hello {name}!</span>; | |
describe('name component', () => { | |
it('should render the name', () => { | |
const wrapper = shallow(<NameComponent name="foo" />); | |
expect(wrapper.type()).toBe('span'); |
Not sure, if these are all valid.
I basically want to add links to my data. In HAL it probably would lool like this:
{
"_links": {
"self": {
"href": "https://example.com/users/1"
},
I don't know, if it is correct to use IANA relations in this way and to add custom relations.
But these examples are parsed in the same way.
inlined relations
{
"http://www.iana.org/assignments/relation/self": {
"@id": "https://api.example.com/users/1"
11433 execve("/bin/ping", ["ping", "google.com"], [/* 14 vars */]) = 0 | |
11433 brk(NULL) = 0xc9b000 | |
11433 fcntl(0, F_GETFD) = 0 | |
11433 fcntl(1, F_GETFD) = 0 | |
11433 fcntl(2, F_GETFD) = 0 | |
11433 access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory) | |
11433 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) | |
11433 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) | |
11433 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 | |
11433 fstat(3, {st_mode=S_IFREG|0644, st_size=33275, ...}) = 0 |
18154 execve("/usr/bin/xsel", ["xsel"], [/* 18 vars */]) = 0 | |
18154 brk(NULL) = 0x1cbc000 | |
18154 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) | |
18154 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) | |
18154 open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 | |
18154 fstat(3, {st_mode=S_IFREG|0644, st_size=48267, ...}) = 0 | |
18154 mmap(NULL, 48267, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fda9d0d2000 | |
18154 close(3) = 0 | |
18154 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) | |
18154 open("/usr/lib/x86_64-linux-gnu/libX11.so.6", O_RDONLY|O_CLOEXEC) = 3 |
// works in current chrome (logs from 1 to 5 every second) | |
function sleep(milliseconds) { | |
return new Promise(resolve => setTimeout(resolve, milliseconds)) | |
} | |
async function* seconds() { | |
let second = 0; | |
while (true) { | |
await sleep(1000); |
This is a very basic example which shows how you can create a simple ESLint rule with @ts-check
support. This example features the rule and a test. The rule checks, if you pass an absolute URL to a history.push
function or not.
If you want to use this rule in your ESLint configuration without publishing the rule there is a caveat. AFAIK you can't simply include the path to your rule in your .eslintrc.js
(correct me if I'm wrong). You need to pass the directory of this rule to the CLI as --rulesdir "./path/to/rules"
and if you use VS Code with the ESLint extension you need to set "eslint.options": { "rulePaths": ["./path/to/rules"] },
in your settings.json
as well. Only then you can add the rule to your config:
module.exports = {
// ...yourCurrentConfig,
rules: {
// ...yourCurrentConfig.rules,
'some-rule': 'error'