Match player selection

When a match is created, players can be chosen as follows:

• Team 1
• Player one
• Player two (if doubles match)
• Team 2
• Player three
• Player four (if doubles match)

If the match is set to a singles match, players two and four are hidden from view.

Dropdown Search field

In the future, if there are too many players to choose from, having a searchable dropdown field is going to be super valuable.

The select2 package looked good, and I had implemented and pushed it into production.

However this was premature as it caused some bugs:

1. Setting match combination to a singles match didn't hide player two and four from the form
2. The width of the dropdown fields became inconsistent.

Solution

I've rolled back the implementation of select2 dropdown fields.

I'll continue testing how to implement it properly before I push it through to production again.

It's a good lesson to conduct more thorough testing before pushing changes to production.

Changes

Match "notes" are now "comments"

The "notes" feature available under individual matches are now called "comments".

The interface for adding comments is also simplified so users don't need to navigate a series of buttons to add a comment.

Added

Matches pagination

The load times of the Matches page was taking a while as the query to extract all the data for all matches took a long time.

This page has been paginated to show 10 matches per page, improving the load times and hopefully user experience.

Bug Fixes

Comments

Previously, adding a comment would display in the chat section, but the new comment form wouldn't save a new comment.

The HTMX has been fixed, and Alpine.JS has been removed. Users no longer need to refresh the page to add comments in quick succession.

This should now feel more like a standard messaging app.

Match completion and verification buttons

Individual matches can go from creation through completion and verification stages.

Clicking the relevant button would submit data and progress matches through the queue, but the buttons would not update until the page was refreshed.

HTMX is now implemented properly to update the buttons without the user having to refresh the page. Another win for UX!

Bugs

Follow button

The follow button underneath the avatar of each profile page was technically working, but the heart icon was not updating without refreshing the page to provide users an immediate feedback on whether it worked or not.

This has been fixed and the heart icon is filled when a profile is followed, and not filled when unfollowed without having to refresh the page.

What's not to 💖 about this?

Video link error

Adding a YouTube video to a match would result in an error, but the link was being saved.

This was caused by an incorrect redirect url.

This has been rectified.

Matches not recorded against sessions

Users can create matches directly from the session page, but the match wasn't being saved against the session.

This has been fixed too.

Finalise session without price error

The price of a session can be set in two ways:

1. A default price set at the club level
2. Overwrite the default club price by setting the price at the session level

It's possible to not set a price at either club or session level.

In this instance, the Profit and Loss statement results in an error because multiplying the number of attendees by nothing is... 🥁... NOTHING!

A quick fix is now applied where the Profit and Loss statement multiplies the attendees by either the price, or if it is null then $0.

Others

A few minor improvements have also been introduced:

• Match status can now be set to 'incomplete'
  • i.e. for matches that don't go all the way up to 21 points, or when a session has run out of time to fully complete a match
• Past sessions are ordered by descending date
• Recent matches are ordered by descending ID
• Upcoming sessions are ordered by descending date