[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: |
|
||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||
| Description |
|
Some of the RAML 1.0 definitions are out of date from the master definitions. The pageable trait is defined significantly differently: |
| 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? |