us-cbp / gtas-ui Goto Github PK

Need to build a separate fetch to pull unique airport lists from existing data. Size will determine how we cache it.

Modal should close on submit
Error or success notification should display
grid data should refresh

The front-end is forced to build a watchlistspec item, which only the backend should have knowledge of, when it saves new watchlist items. This is bad practice. Need to refactor this so that object info is not leaked out of the service layer. The frontend should free to pass regular form data and leave the service to handle the required transform.

The new code type tab list has the same style (same control) as the admin tab list directly above it. Looks like an extension of the same. We have an existing alternative in Bootstrap, see the flights page.

This will either be an aggregate count of the hits or an icon indicating the most severe type found. Or both.

Cotravelers should be grouped together in the grid

the authentication fetches should be consolidated to a single call returning user details. Unused fields should be eliminated.

• Fetch event notes after adding a new notes
• Use rich text editor (may be Draft.js ? ) to add notes
• Multi select for note types

Query/Rule page is the default grid page
QB component in a modal
grid contains edit icon to launch populated modal
how to handle run query/rule?

We should consider either preventing duplicates on the backend, allowing deletes on watchlist items, or both.

Password needs to have password confirmation. These fields need to validate pre-submit.

Email needs to validate pre-submit.

Must have at least 1 role selected.

The endpoint for the put on a specific code for "Restore" accepts an entire code object in the body of the request rather than just an Id.

Research how it works and either adjust the end point to accept just an id, or change the calling function to provide the entire code object.

Need to implement a dev mode to see failed translations
Add the tag handler back into Table component
other components??

tabs should share the fetch and polling mechanism so that the tabs are just a quick view of the same data filtered differently.

Not critical, but data refreshes should be avoided when no update is submitted or when an update failed.

We should also keep the modal live if an attempted update returns an error.

User data can't be changed by an admin without also updating (and knowing) the user's password. We have removed the password from the dataset returned to the client since this will never be displayed, so a separate password reset dialog and endpoint should be created to handle this.

The existing PUT endpoint also needs to be updated to not expect the password.

The current input form works one email at a time for external email notification.
We should be able to add emails separated by space, comma and semicolon in the input field.

On Passenger Current hits summary, Hits condition text is not readable. There is no space between words and no sentence ending period(.) for each condition.

Steps to reproduce the behavior:

1. Go to Passenger Detail page for hit related passenger
2. Click on Summary tab
3. Notice Hits condition text is not readable.

Expected behavior
Hits condition text is readable.
Screenshots
Please see the Screenshots

Desktop

• OS: Windows
• Browser chrome
• Version 1.13

Make the keys for PNR segment list unique

Modal should close on submit
Error or success notification should display
grid data should refresh

Insure minimal and correct input types are required and validated against for each airport,country, and carrier code submission.

Need to include the Main component in all pages to ensure the content allows room for the Table component's fixed footer. possibly restructure this everywhere later and use Main as a wrapper for pages with a table as the dominant element. or something.

need to review all for issues.

1. move all to /api
2. correct fetch methods where possible
3. reduce footprint where possible

Saving new settings data initially updates the DB, but subsequent saves/refreshes wipeout some of the fields in the DB and GET fetches after that return 500 errors.

Backend returns a 302 (redirect) and the old login page html when a fetch is attempted after session timeout. We need to reconsider the response code, and remove the html body on the backend, and handle the new response with a logout.

Secondarily, need to coordinate the front and backend session lengths. The front end should not be live after the server terminates the session. (separate ticket)