Skip to content

consider brining chota styles in the repo #165

@mr-zwets

Description

@mr-zwets

consider brining chota styles in the repo

Goal: reduce Quasar/chota global CSS collisions while keeping current UI unchanged.

chota shipped size in your install:
dist/chota.min.css: 18,365 bytes
gzipped: 3,614 bytes (~3.5 KB)
Source is already split into 9 small files:
_grid.css 5.5 KB, _form.css 4.2 KB, _util.css 2.9 KB, _base.css 2.7 KB, then smaller _nav/_tab/_tag/_card/_dropdown.
Given your Quasar conflicts (.row, .col overrides in src/css/app.css), the biggest conflict source is clearly _grid.css.

Effort to decide what to keep is moderate, not huge: about half-day to do properly.

Practical plan (low risk):

Create local src/css/chota-subset.css using chota source files as reference.
Start by keeping only what you visibly use: likely _form (for .button, .grouped) + _tab (for .tabs) and required variables from _base.
Exclude _grid.css first (highest conflict with Quasar).
Test key screens (wallet, tokens, settings, dialogs, mobile widths).
Remove @import 'chota'; once subset is stable.
So yes: bringing full chota into repo is easy size-wise, but I’d recommend curated subset import over vendoring the whole framework. That gives AI/code navigation benefits and reduces framework collision risk.

_grid.css — should be dropped first; it defines .row/.col/.container and is the main Quasar conflict source.
_nav.css — no .nav usage in your templates.
_card.css — no chota .card usage (you use Quasar cards / custom classes).
_tag.css — no .tag usage.
_dropdown.css — no details.dropdown usage.
About the ones you asked:

_tab.css — likely relevant (WalletPage.vue uses class="tabs").
_form.css — definitely relevant (button, grouped are used a lot).
_base.css — likely relevant (global variables/reset styles that your app css builds on).
_util.css — probably not needed, but verify carefully since class names like text-center overlap with Quasar and can be ambiguous.
So the safest first cut is: remove 5 files above, keep _base + _form + _tab for now, then evaluate _util separately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions