ultrablue/sillaj-l

A re-coding of the Sillaj time tracker tool using the Laravel php framework.

sillaj-l's Issues

Attempting to run migrations in PROD results in an error: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes

This error appears a few times:

'''
$ php artisan migrate

---

• Application In Production!     *
  

---

Do you really wish to run this command? (yes/no) [no]:

yes

Migration table created successfully.
Migrating: 2014_10_12_000000_create_users_table

In Connection.php line 685:

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes (SQL: alter table users add unique users_email_unique(email))

In Exception.php line 18:

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes

In PDOStatement.php line 112:

SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 1000 bytes
'''

Ensure that the application is ISO 8601 compatible.

The site responds with a time out error if left open for too long

How do we adjust the time out and the behavior? Can it do something like
Logout after n hours of inactivity?

The register page is unstyled.

Remove the listed items from the Events list

We don't need the Event ID.
Change Task ID to Task.
Change Project ID to Project.

What about moving the Events list over to the right of the Entry form?

If there's just a start time, an untrapped error happens.

I'm pretty sure it should be ok to have Events that have just start time or just end time. That way, I can create a new Event when I start, and come back and fill in the end time later. Ditto with the end time.
In addition, this lends itself to automatically creating start/end times.

Here's the error:
ErrorException thrown with message "A non-numeric value encountered"

Stacktrace:
#55 ErrorException in /var/www/sillaj-l/app/Http/Controllers/EventController.php:83

Add Clients to Projects

The idea here is to add a Client to Projects. So, rather than saying "IT: Some Project," there would be a Client chooser that would contain IT.

Convert to Livewire

This is a major change, I think. I may need to keep a long-running feature branch open for it and smaller bug fix and enhancement branches open.

When a field (or fields) isn't (aren't) updated, highlight it (them) to show which field (fields) failed.

I don't see a way to delete Events

Oops! 🥴

Don't let toasts move other content around

When editing Events, the toast that appears pushes the Event List down. It shouldn't.

The Events List looks like it's not Tailwind-ified.

Create a HomeController for the dashboard.

Making EventsController the home controller isn't a good idea.

Ensure that FormDate defaults to today's date when creating a new Event. When editing an existing Event, it should be that Event's date.

The page header isn't styled

When editing a date other than Today, the Event editor forgets which day it's displaying

If I select a date in the Calendar, the Event entry/edit area doesn't update to show that date in the date field.

Also, if I create a new Event for that date, it creates the Event, but it goes back to the default date (today).

So, it probably needs a way to remember the currently selected date.

The Tasks list isn't sorted

In the main dashboard, the list of Tasks isn't sorted.

Consolodate AJAX calls

See if you can get the various AJAX calls to go into a single function or something.

Please update the date entry field to use Date Input Component with Vue

https://github.com/maoberlehner/building-a-date-input-component-with-vue
https://markus.oberlehner.net/blog/building-a-date-input-component-with-vue/

https://vegibit.com/laravel-vue-component-example/

Consolodate the toast JavaScript into a function or something

Make a function or something; like this:

showToast(type = success|failure, headerText, BodyText) {

   function setDisplayTime();
   etc...
}

Is it possible to have the page check to see whether the user is still logged in and if not, refresh to the login page?

If my session has expired, and I attempt to create or edit an Event, it'll probably result in an error and lost data?

I suppose it's worth asking whether we can store POSTs during a login?

We should never, ever make the user repeat themselves.

In the Events list, highlight Events that don't have complete data

In other words, that that are missing Start Times, End Times, etc.

Add a way to edit Events from the main dashboard

There's no way to edit the Events in the Event List. Add a link or something.

In deployed version, Tasks isn't updating when a new Project is selected in the Projects dropdown

Hm.

Set the date field's default entry to the currently edited date.

Consolidate Meetings Tasks

This is specific to my data.
See about consolidating Meetings Tasks. You have 16 different kinds of meetings, including at least one duplicate. They probably should be reduced to just one: Meetings. And the type appended to the description.

The Event Editor shows '60' for the minutes sometimes

Probably at the top of the hour.

The Project field in the Event editor should autocomplete

Event Editor: is it possible to have it save on CTRL/CMD S or something?

The issue is that in the Description field, I have to tab out to save. Is it possible to have it save when that field is active?

Disable the Task List while it's being updated.

📊 Add Reporting Feature, please

Times like 10: break Events

Carbon\Exceptions\InvalidFormatException
Could not parse '10:': DateTime::__construct(): Failed to parse time string (10:) at position 0 (1): Unexpected character

Change the order of columns in the Event List

Current:

• ID
• Project
• Task
• Start
• End
• Duration
• Description

Proposed:

• Start
• End
• Duration
• Project
• Task
• Description
• Remove ID

Thanks!

Change the emoticon in the Title depending on the environment (dev, prod)

It needs a way to hide archived Projects (and Tasks)

There a a number of Archived Projects. They're just noise.
But, I never considered a way of archiving them. Maybe a soft-delete? Also, there's the show column. I don't think it's being used at all now.

Please add :hover styles to the Calendar Nav.

Maybe fish eye them??

Add Project and Task tallies to the Tasks list.

For current day and current week.

Update the Calendar Nav to use divs and flexbox

Remove .env.testing and update gitignore

Update jQuery to 3.4.0

https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/

Allow Projects to be color-coded

This will help with visually grouping Events.

In the Event editor, if start time and end time are both populated, then duration should be disabled.

Also, check to see the rules regarding ( ( Start Time OR End Time ) AND Duration ). I thought that if Start Time and Duration are present, then End Time is calculated from them? Same for Start Time if End Time and Duration are populated. In those cases, the interface should behave the same way. This will help to eliminate mistakes and make it clear what's happening on the back end.

Duration is broken

When entering a duration, it requires AM/PM. That's not a Duration, that's a time.
In addition, when I do use AM/PM, and later try to list the Event (such as in the Dashboard for that day), I get an Whoops error:

DateTime::modify(): Failed to parse time string (:0) at position 0 (:): Unexpected character (View: /home/sillaj-l-01/public_html/sillaj-l/resources/views/partials/events-list.blade.php) (View: /home/sillaj-l-01/public_html/sillaj-l/resources/views/partials/events-list.blade.php)

On the Event editor, make the Save button show when it has focus

Set the start time's value to now

Only when it gets focus?

Add a tooltip to show long Descriptions

It would be good to have a way show entire descriptions. Tooltips are one way.

Make the Event Editor put most frequently used Projects and Tasks at the tops of their list

So maybe sort by:
Used
Alpha

Remove the ability for users to add themselves

It's probably better to have an admin page.

But then, what about the first user? Hmmmm.

Entering hours only in the Event Editor results in an error

Entering a number like 12 results in an error:
Undefined offset: 1

app/Http/Middleware/processTemporalInputs.php:104

It should either be validated or accepted as an hour without minutes.

So:

if ( $timeString has 1 or 2 digits  &&  $timeString >=0 && $timeString <= 24) {
   $hours = $timeString;
   $minutes = 0;
} else {
   The input isn't legal.
}