Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

The BSDs let you pass path names longer than sizeof(s.sun_path), they read past the end when socklen > sizeof(struct sockaddr_un) up to a limit¹. Let's support that.

¹ I'm 80% sure it's 255 on all BSDs but it certainly is on Darwin and FreeBSD.

Since ESLint doesn't let us disable auto-fix for individual rules, and the capitalized-comments rule, while useful, can be annoying in editors when "auto-fix on save" is enabled.

SamVerschueren/vscode-linter-xo#78 (comment)

It's not recommended to use document.cookie directly as it's easy to get the string wrong. See sindresorhus/eslint-plugin-unicorn#299 and https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie Instead, the user should use a cookie library.

I guess we should only prevent setting document.cookie? There might be valid reasons to read it?

Summary

👋 your task, should you choose to accept it, is to add names (like, for people) to Cryptozoologist.

Acceptance criteria

• As a user of the Cryptozoologist gem, I can call the method Cryptozoologist.name and be provided with a string that uses the internal dictionaries (of your choice) to make a person's name (Petunia Pygmy Puff, Samaria Aquamarine, Akari Jumpsuit)

It would be useful for the case workers to be able to see a log of the progress in a case file.