projectwallace / projectwallace/projectwallace.com

Preload data when ?url= is present

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

Nobody has claimed this yet.

page: analyze-css page: css-code-quality page: custom-property-inspector page: design-tokens platform: usability
Dominant language
Svelte
Stars
3
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
11

Description

We used to have this years ago, forgot why I removed it. Maybe it was because the triangle hoster was billing me big time for CPU time, dunno.

Considerations

  1. When ?url= is present, scrape immediately, without user having to press 'analyze css'
  2. Watch out for slow first contentful paint, maybe show a loading state first
  3. Add heaps of tests, a lot of existing tests will have to be rewritten

Contributor guide

No contributing guide indexed for this repository

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

Start by tracing the existing “analyze css” flow and how the app handles a ?url= query parameter. Review the existing tests before changing behavior, then verify that a URL triggers scraping automatically, a loading state appears promptly, and the relevant tests pass without regressions.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.