Closed asherlloyd closed 9 months ago
I can "fix" those errors by changing the type of those colors to string
instead of a more TypeScript type safe type. How's that strike you?
I can "fix" those errors by changing the type of those colors to
string
instead of a more TypeScript type safe type. How's that strike you?
Resolved via defining the Tailwind config within a TypeScript file rather than the decoration listed in Tailwind's documentation:
/** @type {import('tailwindcss').Config} */
Description
This MR enables routing for prayer decks and cleans up the visuals somewhat.
Reason
To resolve some of the issues on #29, mostly relating to MVP prayer deck stuff
How this has been tested
Local testing of the frontend in development mode yielded no issues - however, the build (
yarn build
) is throwing errors related to the Tailwind config. It isn't recognizing the custom configuration items. TODOTypes of changes
Screenshots
Checklist: