Skip to content

Commit

Permalink
Merge pull request atom#757 from atom/fix-broken-build
Browse files Browse the repository at this point in the history
Fix failing CI
  • Loading branch information
darangi authored Feb 21, 2022
2 parents 43ddf24 + e39b219 commit ac43e16
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion Gemfile
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
source 'https://rubygems.org'
ruby '2.6.8'
ruby '2.6.9'

# essential
gem 'nanoc', '~> 4.7'
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ module.exports = {
}
```

Similarly, to consume a service, specify one or more [version _ranges_](https://docs.npmjs.com/cli/v7/using-npm/semver#ranges), each paired with the name of a method on the package's main module:
Similarly, to consume a service, specify one or more [version _ranges_](https://docs.npmjs.com/cli/v6/using-npm/semver#ranges), each paired with the name of a method on the package's main module:

```json
{
Expand Down
2 changes: 1 addition & 1 deletion content/hacking-atom/sections/package-word-count.md
Original file line number Diff line number Diff line change
Expand Up @@ -471,7 +471,7 @@ From here you can inspect objects, run code and view console output just as thou

Your package should have tests, and if they're placed in the `spec` directory, they can be run by Atom.

Under the hood, [Jasmine v1.3](https://jasmine.github.io/1.3/introduction.html) executes your tests, so you can assume that any DSL available there is also available to your package.
Under the hood, [Jasmine v1.3](https://jasmine.github.io/archives/1.3/introduction) executes your tests, so you can assume that any DSL available there is also available to your package.

##### Running Tests

Expand Down
6 changes: 3 additions & 3 deletions content/hacking-atom/sections/writing-specs.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: Writing specs

We've looked at and written a few specs through the examples already. Now it's time to take a closer look at the spec framework itself. How exactly do you write tests in Atom?

Atom uses [Jasmine](https://jasmine.github.io/1.3/introduction.html) as its spec framework. Any new functionality should have specs to guard against regressions.
Atom uses [Jasmine](https://jasmine.github.io/archives/1.3/introduction) as its spec framework. Any new functionality should have specs to guard against regressions.

#### Create a New Spec

Expand Down Expand Up @@ -47,7 +47,7 @@ describe("when a test is written", function() {

##### Add One or More Expectations

The best way to learn about expectations is to read the [Jasmine documentation](https://jasmine.github.io/1.3/introduction.html#section-Expectations) about them. Below is a simple example.
The best way to learn about expectations is to read the [Jasmine documentation](https://jasmine.github.io/archives/1.3/introduction#section-Expectations) about them. Below is a simple example.

```javascript
describe("when a test is written", function() {
Expand Down Expand Up @@ -160,7 +160,7 @@ describe("fs.readdir(path, cb)", function() {
})
```

For a more detailed documentation on asynchronous tests please visit the [Jasmine documentation](https://jasmine.github.io/1.3/introduction.html#section-Asynchronous_Support).
For a more detailed documentation on asynchronous tests please visit the [Jasmine documentation](https://jasmine.github.io/archives/1.3/introduction#section-Asynchronous_Support).

#### Running Specs

Expand Down

0 comments on commit ac43e16

Please sign in to comment.