You are browsing as a guest. Sign up (or log in) to start making projects!

4h 37m 3s logged

Devlog

I forgot to add that I worked on the tests in the test branch, not the main one.

  • OAuth2 PKCE testing.
    • Helped me find an error where, if the code was used (it was reset to ""), it was accepted as "".
        Now it correctly returns an error.
  • OAuth2 flow testing.
  • Warnings and diagnostics now have some simple checks too.

And I merged it into main.

Then I started cleaning up the Tailwind CSS.

NOTE: they are in new branch dashboard/cleanup

Why? Because I used the Play CDN in the past, so I couldn’t create utility classes in a CSS file.

Soooo I didn’t. Andddd there were a lot of Tailwind classes that didn’t fit on my screen.

Now that I started precompiling it, I could add them.

I added 5 unique utility classes. All of them combined are used around ~120 times across all HTMLs.

The longest one:

@utility inputSelection {
   @apply w-full px-4 py-2.5 bg-zinc-950 border border-zinc-800 rounded-xl text-zinc-100 focus:outline-none focus:ring-2 focus:ring-blue-300 focus:border-transparent transition-all appearance-none text-center [text-align-last:center] cursor-pointer;
}

I also minified the CSS file. If I understand it, it removes anything the browser doesn’t need to understand the CSS (new lines, unnecessary spaces…). It’s better because those characters are still sent over the network, and fewer bytes mean less traffic.

While using the new utility classes, I tried to preserve the layout, so everything should look the same as before.

0
19

Comments 0

No comments yet. Be the first!