Repository navigation
1.2.1
laya-php now works with any server that follows TypeSafe's OpenAPI spec for POST /v1/systemone, such as sys1, not just laya-serve. CI now checks requests and responses against that spec on every change and every week.
Fixed
- Answers without
answer_confidence. Servers that only follow the spec don't sendanswer_confidence. Before,answerConfidencewas0.0for them, so everyminConfidencecheck failed. It now falls back to the answer'sconfidence. If a yes/no answer has noconfidenceeither, it gets laya's ownmax(P(yes), P(no)). Thresholds andminConfidencekeep working, thoughconfidenceis stricter than the calibrated value for choice and score answers. - Requests always name a model. The spec requires a
modelstring. When you don't pin aModel, requests now send"model": "jev-latest"instead of leaving the field out. laya-serve still routes by language for that name, and sys1 reads it as the model it serves.Laya::fake()still reportsnullto assertions when laya routes, so tests don't change.
Upgrading
No breaking changes and no new requirements. The only change on the wire is the model field on requests that don't pin a checkpoint. laya-serve routes them the same as before, but the cache key includes the request, so those requests miss the cache once after you upgrade.
Full Changelog: 1.2.0...1.2.1