utdallasepics / caccc_resource_database Goto Github PK

If something doesn't exist, server shouldn't crash but should instead return a message to the front end.

No more overly crowded state columns (with full state name text in one narrow column)
Default selected 'TX' value for ease of use

Allows users to delete and add resources without disruptive pop-ups

Node code should not be managing database, nor should it require the user to have a TTY open (running from the bat file)
Mongo service should be started via npm script, and build system should use npm scripts to manage node_modules instead of them being committed to git

Example: npm run server
in package.json:
"scripts": {
"server": "concurrently 'mongod --config ./mongo.conf' 'node server.js'"
}
Alternatively, mongod can be configured as a service.
Remove associated orchestration and config code from server.js, paths should be set via .env instead of as flags

• submission of referrals should be separated from editing.
• create a "view" for resources, where we can view an overview of everything (possibly including viewing of referral statistics here)
• referral view UI should be better than an alert!
• delete specific attachments
• node docker image
• cleaner error communication - all pages should support displaying an error message and we should always return a message to the user

Instead of using sync operations (eg fs.readdirSync), use asynchronous operations to prevent blocking on IO. Look at async/await syntax.

View dates on individual referrals

Tight coupling between views and API makes it hard to reason about what is happening. Instead of GET requests for everything, those should be limited to loading of pages. Updates and deletions should be performed as individual requests that do not reload the whole page, but instead update small chunks such as displaying a success/error dialog.

Possibly look into Vue/Nuxt or similar framework for the frontend to help with conceptual/organizational separation of frontend/backend. You can go with either an SPA or a static site for the frontend.

No longer have to delete an entire resource to just delete a PDF

No more disruptive pop-up for viewing failures

Decrease green border size to make better use of viewport

The layout of the table should not be disrupted when the window is resized

Website and Links are hyperlinked.

No more crowding the narrow state column with excessive text (full state names)

Several areas could use splats instead of manual assignment, eg the insertRecord function in resourceController could be expressed better as

resource = {... req.body, processResouceType(req.body.resourceType), resourceReferrals = 0} etc

Don't need to delete an entire resource anymore in order to remove a PDF

Current deployment and update depends on cloning this repository in its entirety, including the whole node_modules folder. This is generally considered Bad Practice.

Ask Taz about Github releases and the proper way to handle dependencies.