kripod / kripod/otion

Use Records as the input of `css` on the long term

Open
#51 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
624
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Motivation

As suggested by this article, hashing could be avoided for identical style records. This could increase performance, possibly with low efforts.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue concerns the css input API and proposes Records to avoid hashing identical style records. Start by locating the css entry point and reviewing the linked Records article; done would require a decided API direction and evidence that the change improves performance without breaking existing inputs.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.