2024-06-05 11:27:06 +08:00
|
|
|
# frozen_string_literal: true
|
|
|
|
|
2024-07-03 06:45:37 +08:00
|
|
|
RSpec.describe(Flags::ReorderFlag) do
|
2024-10-17 23:15:35 +08:00
|
|
|
describe described_class::Contract, type: :model do
|
|
|
|
it { is_expected.to validate_presence_of(:flag_id) }
|
|
|
|
it { is_expected.to validate_inclusion_of(:direction).in_array(%w[up down]) }
|
2024-06-05 11:27:06 +08:00
|
|
|
end
|
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
describe ".call" do
|
DEV: Provide user input to services using `params` key
Currently in services, we don’t make a distinction between input
parameters, options and dependencies.
This can lead to user input modifying the service behavior, whereas it
was not the developer intention.
This patch addresses the issue by changing how data is provided to
services:
- `params` is now used to hold all data coming from outside (typically
user input from a controller) and a contract will take its values from
`params`.
- `options` is a new key to provide options to a service. This typically
allows changing a service behavior at runtime. It is, of course,
totally optional.
- `dependencies` is actually anything else provided to the service (like
`guardian`) and available directly from the context object.
The `service_params` helper in controllers has been updated to reflect
those changes, so most of the existing services didn’t need specific
changes.
The options block has the same DSL as contracts, as it’s also based on
`ActiveModel`. There aren’t any validations, though. Here’s an example:
```ruby
options do
attribute :allow_changing_hidden, :boolean, default: false
end
```
And here’s an example of how to call a service with the new keys:
```ruby
MyService.call(params: { key1: value1, … }, options: { my_option: true }, guardian:, …)
```
2024-10-18 23:45:47 +08:00
|
|
|
subject(:result) { described_class.call(params:, **dependencies) }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
fab!(:current_user) { Fabricate(:admin) }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
let(:params) { { flag_id: flag_id, direction: } }
|
|
|
|
let(:dependencies) { { guardian: current_user.guardian } }
|
|
|
|
let(:flag_id) { flag.id }
|
|
|
|
let(:flag) { Flag.order(:position).last }
|
|
|
|
let(:direction) { "up" }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
context "when contract is invalid" do
|
|
|
|
let(:direction) { "left" }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
it { is_expected.to fail_a_contract }
|
|
|
|
end
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
context "when model is not found" do
|
|
|
|
let(:flag_id) { 0 }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
it { is_expected.to fail_to_find_a_model(:flag) }
|
|
|
|
end
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
context "when user is not allowed to perform the action" do
|
|
|
|
fab!(:current_user) { Fabricate(:user) }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
it { is_expected.to fail_a_policy(:invalid_access) }
|
2024-06-06 07:40:14 +08:00
|
|
|
end
|
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
context "when move is invalid" do
|
|
|
|
let(:direction) { "down" }
|
2024-06-05 11:27:06 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
it { is_expected.to fail_a_policy(:invalid_move) }
|
2024-06-05 11:27:06 +08:00
|
|
|
end
|
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
context "when everything's ok" do
|
2024-10-22 16:07:24 +08:00
|
|
|
# DO NOT REMOVE: flags have side effects and their state will leak to
|
|
|
|
# other examples otherwise.
|
DEV: Provide user input to services using `params` key
Currently in services, we don’t make a distinction between input
parameters, options and dependencies.
This can lead to user input modifying the service behavior, whereas it
was not the developer intention.
This patch addresses the issue by changing how data is provided to
services:
- `params` is now used to hold all data coming from outside (typically
user input from a controller) and a contract will take its values from
`params`.
- `options` is a new key to provide options to a service. This typically
allows changing a service behavior at runtime. It is, of course,
totally optional.
- `dependencies` is actually anything else provided to the service (like
`guardian`) and available directly from the context object.
The `service_params` helper in controllers has been updated to reflect
those changes, so most of the existing services didn’t need specific
changes.
The options block has the same DSL as contracts, as it’s also based on
`ActiveModel`. There aren’t any validations, though. Here’s an example:
```ruby
options do
attribute :allow_changing_hidden, :boolean, default: false
end
```
And here’s an example of how to call a service with the new keys:
```ruby
MyService.call(params: { key1: value1, … }, options: { my_option: true }, guardian:, …)
```
2024-10-18 23:45:47 +08:00
|
|
|
after { described_class.call(params: params.merge(direction: "down"), **dependencies) }
|
2024-10-22 10:18:57 +08:00
|
|
|
|
2024-10-17 23:15:35 +08:00
|
|
|
it { is_expected.to run_successfully }
|
|
|
|
|
|
|
|
it "moves the flag" do
|
|
|
|
expect { result }.to change { Flag.order(:position).map(&:name) }.from(
|
|
|
|
%w[notify_user off_topic inappropriate spam illegal notify_moderators],
|
|
|
|
).to(%w[notify_user off_topic inappropriate spam notify_moderators illegal])
|
|
|
|
end
|
|
|
|
|
|
|
|
it "logs the action" do
|
|
|
|
expect { result }.to change { UserHistory.count }.by(1)
|
|
|
|
expect(UserHistory.last).to have_attributes(
|
|
|
|
custom_type: "move_flag",
|
|
|
|
details: "flag: #{result[:flag].name}\ndirection: up",
|
|
|
|
)
|
|
|
|
end
|
2024-06-05 11:27:06 +08:00
|
|
|
end
|
|
|
|
end
|
|
|
|
end
|