No Application Message on Tables for Admins and Recruiters #205
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ℹ️ Issue
Closes an issue where no applications can render a table, which can confuse the user. Now, when there are no applications, the user on the admin/recruiter panel will receive a message indicating there is no application at this time.
📝 Description
Changed mostly the index.tsx, where, when showEmpty (showEmpty checks for the empty application) is true, it would render a centered Box with the message “There are no applications at this time”.
Otherwise, it would render the existing DataGrid with applicationColumns as before.
✔️ Verification
🏕️ (Optional) Future Work / Notes
Logic is, if there is no application, there should be nothing for the admin or recruiter to see. There is no other access to the page unless an application is present. Ran into some weird git stash error when trying to commit and pull on a new branch.