A tool that compares code with a design needs to know what the code contains. An index gives it that without keeping a copy. It answers questions such as "where is Button called with size="xs"?" from facts, not from source files.
What the FISYCO index keeps
The last 30 index runs are kept, and each health score names the commit it was counted from.
How it is built and kept current
The index is built statically. FISYCO reads the files through the Git provider's API and analyses them without a build, a render or a screenshot. Your code is never run.
The first run reads the ui-kit folder in full and up to 600 other .tsx and .jsx files; tests, stories and configs are skipped. Reindex in the design system settings starts a run by hand.
A push to the tracked branch that touches the ui-kit, .tsx, .jsx or package.json files starts a new run. FISYCO also checks the branch every 30 minutes in case a webhook stays silent.
Related
- Connect the design system from code: what the first index run reads.
- Consumer repository
- Component health