Files
openfoodnetwork/spec
Maikel Linke 4f15b5a65b Specify raised error in spec and avoid warning
Before it said:

```
WARNING: Using the `raise_error` matcher without providing a specific error or message risks false positives, since `raise_error` will match when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the expectation to pass without even executing the method you are intending to call. Actual error raised was #<RuntimeError: Cannot use t(".legacy_translation") shortcut because path is not available>. Instead consider providing a specific error class or message. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
```
2023-02-28 15:44:18 +11:00
..
2022-12-08 08:32:11 +01:00
2023-02-14 08:08:20 +00:00
2023-02-16 14:27:21 +01:00
2023-02-24 15:31:18 +11:00
2023-02-24 15:10:19 +11:00
2023-02-24 15:10:46 +11:00
2022-02-16 10:23:22 +11:00