-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/update app to support multi years #334
Feature/update app to support multi years #334
Conversation
…l rebates page) and update styles (shrink buttons, update small screen layout)
…link to the right of the new rebate year select
…on text components for dashboard, helpdesk, and signout (less dry but also less indirection)
… and update rebate year select in allRebates component to use it
…status, and update API to return those values and code to reflect they're now each stored at the year level too
…enrollment period is open or closed
…en enrollment is open or closed
…se it in checkFormSubmissionPeriodAndBapStatus() function
…the post should be allowed or not)
…s (e.g formioFRF2023Url)
…g error messages returned to the client)
…timestamps to use new form abbreviations
…s for controlling each form's open enrollment status
…formio2022.js route file and into a new formio.js utility file (for use in a new formio2023.js route file)
…ew form abbreviations
…ute paths have changed
…to use new route paths
…fig and update formio s3 functions to use it in determining the formio form url
…d of individual form url variables, and remove no longer used individual form url variables
… of referencing the formio formUrl object every time
…023 (and update initial submission data fields to reflect changes made to 2023 FRF)
…cross rebate years
…or use across rebate years
… for use across rebate years
… for use across rebate years
…BAP has implemented their 2023 FRF features
…22 form submissions, and add Formio 2023 FRF submission type
…iveryDate field's value discrepancy between the returned data of null and the rendered value of any empty string
…orrect combo key field can be used, based on the rebate year
…data, and rename 2022 queries and hooks to reflect 2022 rebate year
…r fetching data and rendering content, based on rebate year
…2023 rebates, and update Submissions2023 component to render 2023 FRF submissions in the table
|
||
const router = express.Router(); | ||
|
||
router.use(ensureAuthenticated); |
Check failure
Code scanning / CodeQL
Missing rate limiting High
authorization
|
||
const router = express.Router(); | ||
|
||
router.use(ensureAuthenticated); |
Check failure
Code scanning / CodeQL
Missing rate limiting High
authorization
|
||
const router = express.Router(); | ||
|
||
router.use(ensureAuthenticated); |
Check failure
Code scanning / CodeQL
Missing rate limiting High
authorization
|
||
const router = express.Router(); | ||
|
||
router.use(ensureAuthenticated); |
Check failure
Code scanning / CodeQL
Missing rate limiting High
authorization
|
||
const router = express.Router(); | ||
|
||
router.use(ensureAuthenticated); |
Check failure
Code scanning / CodeQL
Missing rate limiting High
Related Issues:
Main Changes:
Major update to the app to allow for the new 2023 rebate year of submissions. Initially supports the new 2023 FRF form, but lays the groundwork for the remaining two 2023 forms, and future rebate year forms.
Steps To Test:
TODO: