Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paging component props do not match prod on listing templates #19849

Open
2 tasks
Tracked by #20313
laflannery opened this issue Nov 8, 2024 · 0 comments
Open
2 tasks
Tracked by #20313

Paging component props do not match prod on listing templates #19849

laflannery opened this issue Nov 8, 2024 · 0 comments
Assignees
Labels
Accelerated Publishing Defect Something isn't working (issue type) next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.

Comments

@laflannery
Copy link
Contributor

laflannery commented Nov 8, 2024

Description

On next-build, the listing templates have the paging components and the max-page-list-length is not set the same as is is on Prod. This causes the pagination to display differently:

Image

ACs

  • Pagination component props match those used currently in content-build / production
  • Pagination displays and functions the same on next-build pages as it does on Prod
@laflannery laflannery added Accelerated Publishing Defect Something isn't working (issue type) labels Nov 8, 2024
@jilladams jilladams added the Story CMS managed product owned by Facilities team label Dec 5, 2024
@jilladams jilladams changed the title Paging component props do not match prod Story listing: Paging component props do not match prod Dec 5, 2024
@jilladams jilladams added VA.gov frontend CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide labels Dec 5, 2024
@jilladams jilladams added the Needs refining Issue status label Dec 20, 2024
@laflannery laflannery changed the title Story listing: Paging component props do not match prod Paging component props do not match prod on listing templates Jan 22, 2025
@laflannery laflannery added next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. and removed VA.gov frontend CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide Story CMS managed product owned by Facilities team labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accelerated Publishing Defect Something isn't working (issue type) next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.
Projects
None yet
Development

No branches or pull requests

4 participants