Commit 0234035
fix(test): align local Typesense image with v30+ supported range
The integration spec at `spec/typesense/collections_spec.rb:156` expects
each field in the create-collection response to include `truncate_len`,
which was added to Typesense's field schema response in v30.x. The local
`docker-compose.yml` was still pinned to `typesense/typesense:29.0`, so
the spec failed locally with the field missing from the actual response:
Failure/Error: expect(result['fields']).to eq(expected_fields)
Diff: - "truncate_len" => 100,
The README compatibility table already states typesense-ruby v5.0.0
supports Typesense >= v30.0, so this just realigns local development
with the gem's stated server compatibility.
Bumping to the latest stable patch (30.2) also surfaced two new fields
on curation rule responses (`stem`, `synonyms`); the curation set test
fixtures are updated to mirror them.
After the change:
- `bundle exec rspec` reports 151 examples, 0 failures, 16 pending
(down from 27 pending: 11 specs that were skipped against Typesense
29 are now exercised against 30.2).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent f33f224 commit 0234035
3 files changed
Lines changed: 7 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | | - | |
| 3 | + | |
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
27 | 27 | | |
28 | 28 | | |
29 | 29 | | |
30 | | - | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
31 | 33 | | |
32 | 34 | | |
33 | 35 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
27 | 27 | | |
28 | 28 | | |
29 | 29 | | |
30 | | - | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
31 | 33 | | |
32 | 34 | | |
33 | 35 | | |
| |||
0 commit comments