kripod / kripod/otion

ESLint plugin for keeping the recommended pseudo selector order

Open
#11 0 comments 0 reactions 0 assignees View on GitHub
enhancement help wanted
Dominant language
TypeScript
Stars
624
Forks
22
PR merge metrics
No merged PRs in 30d

Description

## Motivation

Simple pseudos [have a sorting order](https://github.com/kripod/otion/blob/fafda618525945f84abef5aba3a2528821676f3e/packages/otion/src/pseudos.ts) which will be recommended on the long term, even after #1 gets resolved. This should serve as a guarantee for atomic efficiency, generating the least amount of CSS rules possible.

## Details

The recommended configuration should emit an error until [customizable rule sorting](https://github.com/kripod/otion/issues/1#issuecomment-629990765) is implemented. After that, a warning should suffice.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the pseudo-selector order in packages/otion/src/pseudos.ts and the linked discussion for customizable rule sorting in issue #1. Define the ESLint plugin's recommended configuration around that order, including when violations should be errors versus warnings; the issue is complete when the plugin enforces the recommended order as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, typescript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.