bossbuwi / reality-deprecated

Reality is a mirror of existence.

reality

reality has collided with existence

The sources may be found under

src/main/resources/frontend

This repository is now deprecated. Thank you for the support. :)

Love,
bossbuwi

reality-deprecated's Issues

New System Form

Create a form on the system UI to enable users to add a new system. It must have the following:

• Appear when the New System button is clicked on the System tab.
• Must be a dialog box, preferably full screen like the new events form but a smaller one may suffice.

No logic is needed for this, only the UI.

Encrypt local storage

PR #21 changed Vuex's storage from local storage to session storage. This is just a temporary workaround because local storage is much better. It persists even after the browser is closed. It is the next best thing after server side cookies when persisting data between browser sessions.

The following must be done:

• Encrypt local storage to allow Vuex secure storage.
• Move Vuex's storage location back to local storage, nullifying the change done by PR #21

Create events UI

Create the events page UI. It must contain the following:

• List of all events.
• Button to open the new events form.
• New events form (modal).
• (Optional) Ability to edit an event when clicked from the list.

No logic is needed for this, only the UI.

Create systems ui

Create a UI for the systems. No logic is required. It must contain the items below.

• A table showing a list of the systems currently registered on the app.
• A popup showing a system's details if an item on the list is clicked.
• (Optional) A button that will open a form to add a system. Note that this is tagged as optional but it would surely be added later.

No logic is needed for the above items. Logic would be added under a different task/issue.

Rework Calendar View

Calendar view is throwing warnings every so often. And frankly the codes are so messy and substandard. Please rework it, from scratch is possible. Some loss of features are acceptable.

Add delete capability to events

Events cannot be deleted. Nothing shall last forever. Add capability to delete events. The server has already been updated with this feature.

Add role recognition

Certain features, like creating a new system, must be locked behind specific roles, mirroring that of the backend. Add this role recognition feature on the frontend as well.

Modify calendar popup

Change the calendar popup to also display the event's ID.

Create login

• The user must be able to login with the app recognizing that the user has indeed logged in.

Modify endpoints to match with server

The server has changed the endpoints. Modify the frontend to match with the new ones.

Login form render issue

Login form is being rendered weirdly. I can't confirm if it is above the component with just a clear background or if it is rendered inline with the components. Please fix.

• Login form must always be on top, or opaque.

It has been confirmed that the login form is transparent. It needs to be opaque.

Create login form

A login form must be created. The conditions are as follows:

• Must have a username input field. This field must not accept blank and optionally, empty inputs.
• Must have a password input field. This field must not accept blank and optionally, empty inputs. This field must hide the password from plain sight.
• Must have a log in button. The form must validate upon clicking this button.
• Must only be visible if the user is not authenticated, otherwise it is hidden.

This is in conflict with #1
Only one or the other needs to be created. Personally I prefer this instead of a dedicated login landing page because the users need to be able to see events even without logging in. However, putting the login form somewhere on the existing UI is not really good design in my opinion. Decide.

Optimize build

The build output is too large. Do something to reduce the size.

Create new event logic

Add logic on the new event form.

Create Dashboard logic and UI

Dashboard logic means everything under the hood needed to fetch data from the server and display them to the user. No explicit error handling (dialog boxes, popups, etc.) required. Those will be worked on later.

Add rules

Rules for system use must be added on the dashboard. The implementation must be aesthetically pleasing.
The server needs to implement this as well.

Create event popup

Create a popup that will show if an event on the calendar view is clicked. It must show the event details. For now, it may or may not be editable

Finalize app

There are too many features to add that I can't enumerate them all. Just add whatever is needed then finish the app. This might be the last push.

Token expiry

Add a way to track the validity of the JWT stored on the local storage. This must be done locally and without connecting to the server. If the JWT is expired, the stored credentials must be deleted before the app loads to prevent later auth issues.

Create event list view logic

The event list view must fetch and display data from the server. Clear any hard coded data.

Create logic for System list view

The following must be done:

• Remove hard coded data from the systems list view.
• System list view must be able to fetch data from server and display them in tabular form.

The logic for the New System button is not included in this issue.

Create calendar UI

The main calendar UI needs to be created. It must contain the following:

• A calendar, of course. The bigger, the better. And yes, this applies to everything.
• It should display the events for the day, be it on the calendar itself or on a card near it. But it should do this ideally without the user clicking anything, i.e., once the page loads, the events for the day would be displayed.
• (Optional) Displays a detailed event view if an event is clicked.

Create landing page

Create landing page for login. The conditions are as follows:

• Only the login form and optionally, the app bar should be visible at the landing page. The side bar must be hidden.
• The landing page must not trigger an app reload upon login.
• The landing page must be hidden after a successful login.

To show the hiding of the landing page, hard coded, temporary logic may be added.

Create dashboard ui

Create a UI for the dashboard. No logic is required. It must contain the items below.

• Card showing the total number of saved systems.
• Card showing the total number of logged events. (Optional) Can have a button that will show the details of the most recent event logged.
• Card showing the total number of registered users.
• (Optional) Chart showing the number of events logged daily. Note that this may need some consolidation with the back end.

Calendar view logic

• Create the logic for the calendar view. It must be able to fetch and display data from the server. All hard coded values must be deleted and replaced with dynamic ones.