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

Fix typos #537

Merged
merged 1 commit into from
Mar 5, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Changed

- Calling `active_record.reload` resets the adapater's internal cache
- Calling `active_record.reload` resets the adapter's internal cache

## v10.2.1 3rd April 2023

Expand Down Expand Up @@ -450,7 +450,7 @@ No changes from v1.0.0.beta2

### Fixed

- `ActiveRecordModel.in_state` and `ActiveRecordModel.not_in_state` now handle inital states correctly (patch by [@isaacseymour](https://github.com/isaacseymour))
- `ActiveRecordModel.in_state` and `ActiveRecordModel.not_in_state` now handle initial states correctly (patch by [@isaacseymour](https://github.com/isaacseymour))

### Added

Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -269,7 +269,7 @@ end
By default Statesman does not record a transition to the initial state of the state machine.

You can configure Statesman to record a transition to the initial state, this will allow you to:
- Keep an accurate record of the intial state even if configuration changes
- Keep an accurate record of the initial state even if configuration changes
- Keep a record of how long the state machine spent in the initial state
- Utilise a transition hook for the transition to the initial state

Expand Down Expand Up @@ -511,7 +511,7 @@ Raised if:
### Runtime errors

These errors are raised by `transition_to!`. Using `transition_to` will
supress `GuardFailedError` and `TransitionFailedError` and return `false` instead.
suppress `GuardFailedError` and `TransitionFailedError` and return `false` instead.

#### GuardFailedError

Expand Down
2 changes: 1 addition & 1 deletion spec/statesman/machine_spec.rb
Original file line number Diff line number Diff line change
Expand Up @@ -995,7 +995,7 @@ def after_initialize; end
let(:instance) { machine.new(my_model) }
let(:metadata) { { some: :metadata } }

context "when it is succesful" do
context "when it is successful" do
before do
expect(instance).to receive(:transition_to!).once.
with(:some_state, metadata).and_return(:some_state)
Expand Down
Loading