Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Erroneous api-lint validation for mod-patron with new AMF dependency

Description

Each time that we upgrade the api-lint dependency "amf-client-js" we do local testing of all back-end modules. With the recent FOLIO-3553 this was okay for all modules except mod-patron and edge-patron, despite there being no git changes to their sources.

So it is likely an upstream issue.

Raised a ticket at AMF: https://github.com/aml-org/amf/issues/1551

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

David Crossley October 26, 2022 at 4:29 AM

Via upgraded to AMF "amf-client-js" v5.2.0

All okay now.

David Crossley September 22, 2022 at 5:22 AM

The upstream AMF 1551 ticket has a fix. Will be in the next release, due around October 19.

David Crossley September 1, 2022 at 6:07 AM

Blocked awaiting the upstream ticket AMF 1551.

David Crossley August 30, 2022 at 2:05 AM
Edited

The issue was acknowledged upstream.

Our upgrade to AMF v5.0.11 was reverted.

David Crossley August 22, 2022 at 6:55 AM

Doing independent assessment with z-schema shows no problem.

z-schema --pedanticCheck account.json examples/account.json
schema validation passed
json #1 validation passed

Done

Details

Assignee

Reporter

Priority

Sprint

Development Team

FOLIO DevOps

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 22, 2022 at 6:54 AM
Updated October 26, 2022 at 4:30 AM
Resolved October 26, 2022 at 4:30 AM
TestRail: Cases
TestRail: Runs