Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modernize README. #231

Closed
wants to merge 2 commits into from
Closed

Modernize README. #231

wants to merge 2 commits into from

Conversation

wjhsf
Copy link
Contributor

@wjhsf wjhsf commented Mar 2, 2022

Focused on highlighting async methods over callbacks, while trying not to completely rewrite the doc. Also rewrote random other bits and pieces here and there.

Copy link
Member

@awaterma awaterma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be great to rework the statement about AVA and the versions of NodeJS we support; besides that it looks very good to me, and a nice update. Thank you for spending time on this! Greatly appreciated.

Comment on lines +20 to +24
var cookie = await cookiejar.setCookie(cookie, 'https://currentdomain.example.com/path');
var cookies = await cookiejar.getCookies('https://example.com/otherpath');
// Or with callbacks!
cookiejar.setCookie(cookie, 'https://currentdomain.example.com/path', function(err, cookie) { /* ... */ });
cookiejar.getCookies('http://example.com/otherpath', function(err, cookies) { /* ... */ });
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love the comments and examples here!


# API
Inspired by [AVA's support policy](https://github.com/avajs/ava/blob/v4.0.0/docs/support-statement.md), we will follow the [node.js release schedule](https://github.com/nodejs/Release#release-schedule) and support versions that are in Active LTS or Maintenance. We will only drop support for older versions of node when we do a major release.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Inspired by [AVA's support policy](https://github.com/avajs/ava/blob/v4.0.0/docs/support-statement.md), we will follow the [node.js release schedule](https://github.com/nodejs/Release#release-schedule) and support versions that are in Active LTS or Maintenance. We will only drop support for older versions of node when we do a major release.
Similar to [AVA's support policy](https://github.com/avajs/ava/blob/v4.0.0/docs/support-statement.md), we follow the [node.js release schedule](https://github.com/nodejs/Release#release-schedule) and support all versions that are in Active LTS or Maintenance. We will only drop support for older versions of node when we do a major release and in consultation with our community.

I really like the link to AVA's support statement, but we did decide on this policy awhile back. I've tried to make a suggestion that will retain the link, but change the statement to reflect the choices we made earlier a little clearer.


Transforms a domain-name into a canonical domain-name. The canonical domain-name is a trimmed, lowercased, stripped-of-leading-dot and optionally punycode-encoded domain-name (Section 5.1.2 of RFC6265). For the most part, this function is idempotent (can be run again on its output without ill effects).
Transforms a domain-name into a canonical domain-name. The canonical domain-name is a domain-name that has been trimmed, lowercased, stripped of leading dot, and optionally punycode-encoded (Section 5.1.2 of RFC 6265). For the most part, this function is idempotent (calling the function with the output from a previous call will return the same output).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I think this is a much clearer way to express idempotency, nice work)

@wjhsf
Copy link
Contributor Author

wjhsf commented Apr 7, 2022

Closed in favor of #234.

@wjhsf wjhsf closed this Apr 7, 2022
@wjhsf wjhsf deleted the wjh/update-readme branch April 18, 2022 16:52
wjhsf pushed a commit that referenced this pull request Feb 8, 2024
…utomocks (#234)

fixes #232

This PR reverts #231, #210, and #208. They provided functionality to auto mock apex methods.

**Note:** Test authors will need to keep implementing their own apex (+apexContinuation) methods mocks after this PR is merged.

* Revert "fix: apex automock should return a resolved promise (#231)"

This reverts commit 544f95a.

* Revert "fix: add apex stubs to the transformIgnorePatterns (#210)"

This reverts commit fe8381a.

* Revert "fix: automock apex methods with valid wire adapters (#208)"

This reverts commit 125c689.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants