Packet/july 7#21
Conversation
…h submissions - Implement HoneypotField to trap bots in forms. - Create DateField, TextField, and TextareaField components for various input types. - Add DynamicForm to handle form submissions with Freshdesk integration. - Fetch form field configuration from Freshdesk at build time. - Build payload for Freshdesk API submissions, mapping fields appropriately. - Add tests for payload building and form field fetching. - Update Base layout to conditionally load reCAPTCHA script. - Modify Freshdesk handler to support new published research submission route. - Update USWDS theme package references for organizational consistency.
…ching - Integrated dynamic form fetching from Freshdesk with error handling. - enhance Freshdesk form field fetching logic - add unit tests for reCAPTCHA token retrieval
- Changed 'location' field to 'journalName' in the publications schema. - Added optional fields: 'status', 'bdcContribution', 'researchArea', and 'researchCommunity'. - Updated publications.yaml to reflect the new schema, including new entries and fields. - Refactored news page to utilize a PublicationsFilter component and simplified publication data handling.
…age-ui feat(publications): update schema and data structure for publications
…age-ui Feature/bdc enabled research page UI
Feature/form integration
…ssion dismiss functionality
|
i'm seeing a potential discrepancy in the CI lint check and a local check |
mbwatson
left a comment
There was a problem hiding this comment.
looks pretty good! i noted a couple major and a few minor fixes
| * - Research Areas → MultiSelectCheckbox | ||
| * - Org Contributions → MultiSelectCheckbox | ||
| * - Research Communities → MultiSelectCheckbox | ||
| * Reference data options are merged into the relevant field configs before |
There was a problem hiding this comment.
can you say more about/fix this? i see the import of getReferenceDataValues, but i don't see any obvious merging with configs
There was a problem hiding this comment.
this is leftover from when i was thinking about stitching multiple custom objects together (so a publication submission might have reference to a separate research community custom object).
this may still be an option we want to utilize but it can be removed for now, and addressed if we decide to go that route in the future.
There was a problem hiding this comment.
yep that can go until we have the feature
|
|
||
| const { | ||
| variant = 'info', | ||
| style = 'gradient', |
There was a problem hiding this comment.
above comments say style — 'border' | 'gradient'. Defaults to 'border'.
There was a problem hiding this comment.
i think we can remove the 'border' styles altogether. i was mostly testing it out to see how it looked and i think that left border looks too awkward way on the end for a site-wide banner.
| --- | ||
|
|
||
| <Tag | ||
| {...targetUrl ? { href: targetUrl } : { type }} |
There was a problem hiding this comment.
why are we dropping these props?
There was a problem hiding this comment.
one Button instance broken by this is on the Explore page https://github.com/stagecc/bdc-web/pull/21/changes#diff-3764fe46c68134afe78934e871ef9c68ace0e011b21a87c7f3b85cd243d561feR57
There was a problem hiding this comment.
for center, there's a USWDS utility for that
There was a problem hiding this comment.
thank you! that was a mistake.
084fd7d to
c2acfdc
Compare
…in renderCustomObjectField
… and status chip on PublicationsCard
…ility; rename class prop to className to align with react
…isible instead of client:load
…compatibility; rename class prop to className to align with react" This reverts commit 34fbd17.
880a30e to
ba3121d
Compare
mbwatson
left a comment
There was a problem hiding this comment.
👍 good work, this was a hefty one!
| --- | ||
|
|
||
| <Tag | ||
| {...targetUrl ? { href: targetUrl } : { type }} |
There was a problem hiding this comment.
one Button instance broken by this is on the Explore page https://github.com/stagecc/bdc-web/pull/21/changes#diff-3764fe46c68134afe78934e871ef9c68ace0e011b21a87c7f3b85cd243d561feR57
| }} | ||
| aria-label="More information" | ||
| > | ||
| <svg |
There was a problem hiding this comment.
why not use https://designsystem.digital.gov/components/icon/ ?
| --- | ||
|
|
||
| <Tag | ||
| {...targetUrl ? { href: targetUrl } : { type }} |
There was a problem hiding this comment.
for center, there's a USWDS utility for that
| </a> | ||
| </h4> | ||
| <ul | ||
| className="usa-collection__meta margin-top-2" |
There was a problem hiding this comment.
margin-top-2 utility and inline margin-top CSS here
| * - Research Areas → MultiSelectCheckbox | ||
| * - Org Contributions → MultiSelectCheckbox | ||
| * - Research Communities → MultiSelectCheckbox | ||
| * Reference data options are merged into the relevant field configs before |
There was a problem hiding this comment.
yep that can go until we have the feature
Deployment preview available here: https://packet-july-7.d47440bgt2n0.amplifyapp.com/
This PR addresses the following Jira items:
It also addresses Form components and backend infrastructure with the option to use both Custom Forms and Custom Objects. The Published Research Submission form uses a Custom Object.