[FOLIO-1517] Incorrect limit definition in RAML 1.0 trait Created: 19/Sep/18  Updated: 12/Nov/18  Resolved: 19/Sep/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Marc Johnson Assignee: Adam Dickmeiss
Resolution: Done Votes: 0
Labels: core, q3-2018, sprint47
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks MODCXINV-33 Bad pageable Closed
blocks MODNOTES-45 Bad pageable Closed
blocks MODNOTIFY-36 Bad pageable Closed
blocks MODTAG-10 Bad pageable Closed
blocks MODUSERS-89 Bad pageable Closed
Sprint:

 Description   

Some of the RAML 1.0 definitions are out of date from the master definitions.

The pageable trait is defined significantly differently:
RAML 1.0: https://github.com/folio-org/raml/blob/a32eac5e84178134a67a434ea8e055e110e88543/traits/pageable.raml#L11
RAML 0.8: https://github.com/folio-org/raml/blob/90103dffc5d3f55f4ee200f67ff6cf55e4c47d43/traits/pageable.raml#L10



 Comments   
Comment by Adam Dickmeiss [ 19/Sep/18 ]

raml1.0 updated.. Now, we must unfortunately pin to that and release modules one by one.

Comment by Adam Dickmeiss [ 19/Sep/18 ]

As David Crossley pointed out.. searchable.raml was also based on an old version. It's been updated too. Since searchable.raml was only behind WRT example and description, it does not affect runtime.

Comment by Zak Burke [ 20/Sep/18 ]

I have open PRs on the Q3 branches of ui-users and stripes-smart-components to cope with the regression. Merging those two PRs would take care of all the related UI regressions in the Q3 release. Should I go ahead and merge those, or do you plan to get all the updated modules into the Q3 release, in which case those PRs are superfluous?

Generated at Thu Feb 08 23:13:55 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.