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

All published VBA services are not showing on the FE #18214

Closed
2 tasks done
laflannery opened this issue May 24, 2024 · 10 comments
Closed
2 tasks done

All published VBA services are not showing on the FE #18214

laflannery opened this issue May 24, 2024 · 10 comments
Assignees
Labels
Defect Something isn't working (issue type) Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide VA.gov frontend CMS team practice area

Comments

@laflannery
Copy link
Contributor

laflannery commented May 24, 2024

Description

Not all services are showing on the front end on the facilty page. It seems like there might be a max of 10 total set somewhere. For example:

  • Honolulu has 15 published and only 10 showing. The missing ones are and I noticed that those were the most recently published ones:

    • Direct Deposit
    • Education benefits for family members
    • Disability compensation
    • Burial and memorials
    • Benefits letters and decision letters
      image
      image
  • National Capital as 11 published and only 10 showing, again this is the last published one:

    • Home loans
      image
      image

Acceptance Criteria

  • Determine is there should be a limit to how many services display - Answer: no limit
  • All VBA Facility services should appear
@laflannery laflannery added the Needs refining Issue status label May 24, 2024
@laflannery laflannery changed the title All VBA services are not showing on the FE VBA QA: All VBA services are not showing on the FE May 24, 2024
@davidmpickett davidmpickett changed the title VBA QA: All VBA services are not showing on the FE All published VBA services are not showing on the FE May 31, 2024
@davidmpickett davidmpickett added VA.gov frontend CMS team practice area Regional office CMS managed VBA product owned by the Facilities team labels May 31, 2024
@davidmpickett
Copy link
Contributor

There should not a be a limit. All published services should display.

This is a problem and should be investigated ASAP. While this might not technically be blocking of Staging Review (since it is unlikely for Platform to notice) it will be prevent our team from fully testing & QAing VBA.

@davidmpickett davidmpickett added the Facilities Facilities products (VAMC, Vet Center, etc) label May 31, 2024
@jilladams
Copy link
Contributor

jilladams commented Jun 5, 2024

Eli verified: in the code there is no set limit. That makes the missing services more mysterious.
Laura noted: between 2 passes of publishing VBA content, different services did / didn't appear.

@jilladams jilladams added Defect Something isn't working (issue type) and removed Needs refining Issue status labels Jun 5, 2024
@eselkin
Copy link
Contributor

eselkin commented Jun 11, 2024

Turns out Drupal sets a limit to 10 when no explicit limit is set on the subqueries. What is an appropriate limit we should set? 25? 50? 100? I'm guessing we should go with an arbitrarily highish (100) number since we always want to return all services. @Agile6MSkinner @jilladams

@davidmpickett
Copy link
Contributor

Copying my notes from Slack

BLUF: Other places where we are doing queries like this seem to use a limit of 500 (example 1, example 2).

Similar to the epiphany I had in in 17681, this seems to be another reason why VAMCs and Vet Centers call Services as a Field Query rather than a Reverse Node Query. A field query doesn't seem to have a limit (unless the field itself has a cardinality limit).

While adding a limit (here I think?) would be a quick fix, this makes me think that long term we should probably add an Entity Reference field to VBA Facilities to pull in the list of Services (Drupal Config PR) and switch the query to a Field Query (Content build PR). That would make the queries more consistent across facility types and also not having to declare a limit seems more future proof than just picking a high number.

@eselkin
Copy link
Contributor

eselkin commented Jun 12, 2024

Updated my 100 limit to 500 per similar limits, though that's a combined total of 1000 services... Not that any facility will reach that, but that seems like a lot.

@jilladams
Copy link
Contributor

@Agile6MSkinner We need some product help here to decide whether / how to modify the current Drupal implementation. Dave left notes above -- if we do want to align the handling of how we call services acros products, that's new Drupal work & FE template work we need to do to update this implementation. Could you make a note of this for us to talk about in our next refinement, to decide if this is done for now, or if we want to call this tech debt, and clean it up now vs. later?

cc @mmiddaugh

@Agile6MSkinner
Copy link

Agile6MSkinner commented Jun 14, 2024

@jilladams Ok, I've moved this to the top of the order for next refinement.

EDIT: @eselkin @davidmpickett That occurs on Wednesday. If we make a decision then, will that leave us enough time to complete the work by the end of sprint (Tues 6/25)?

@eselkin
Copy link
Contributor

eselkin commented Jun 17, 2024

The work to do the limit increase is in PR (@dsasser is waiting on us resolving whether we want to go ahead wit the limit increase or do the field modifications and changes to graphql). If we change to do the graphql changes and field updates, I doubt that would be done before the end of sprint.

@davidmpickett
Copy link
Contributor

This can't really be verified on prod because no VBAs are published and Preview Server won't show services. So instead I am doing a Content Release on my tugboat with Main & Main (whereas I previously was using PR 2128 for content-build. Once that completes should be verifiable here: https://web-jdujzwgvp8kmj36hcfonqejlgtq5b6st.demo.cms.va.gov/philadelphia-va-regional-benefit-office/

@davidmpickett
Copy link
Contributor

Verified on Tugboat
screencapture-web-jdujzwgvp8kmj36hcfonqejlgtq5b6st-demo-cms-va-gov-philadelphia-va-regional-benefit-office-2024-06-24-14_35_29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defect Something isn't working (issue type) Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

5 participants