[BUGFIX] Feat "benefits" array now render correctly
#776
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eepMoody
approved these changes
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Build Preview
https://deploy-preview-776--open5e-preview.netlify.app/
Description
This PR fixes a bug on the
/feats/[id]page where a feat's benefits (as listed in the"benefits"array) were not being rendered to the page:Resolving this issue required updated the query parameters of the fetch request to the API, and then adding markup to the template tag to correctly render the information returned.
Related Issue
Closes #775
How was this tested?
npm run dev) pulling data fromstagingbranch of the APInpm run test(all tests passing)npm run build(build process completes without error)