You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,11 @@ This repository keeps both shipped UI code and design exploration in the same tr
32
32
- Planned or exploratory ideas may appear in CSS or wireframes before the public API is finished. Those should not be treated as supported integration surface until they are wired into a shipped asset and described in the README API reference.
33
33
- When adding new surface area, update the JavaScript API, README, and runnable examples in the same change so the public contract stays explicit.
34
34
35
+
For production caching, versioned bundle filenames are also emitted as
36
+
`/sf/sf.<crate-version>.css` and `/sf/sf.<crate-version>.js`. Those versioned
37
+
files are served with immutable caching, while the stable `sf.css` and `sf.js`
38
+
paths remain available for compatibility.
39
+
35
40
## Screenshots
36
41
37
42
**Planner123** — Gantt chart with split panes, project-colored bars, and constraint scoring:
@@ -506,6 +511,10 @@ Use `make package-verify` to inspect the exact crate contents that would be publ
506
511
507
512
The verification step checks that required bundled assets and crate metadata are present, and that development-only sources such as `css-src/`, `js-src/`, `scripts/`, and screenshots are not shipped in the published crate.
508
513
514
+
Bundling writes both stable compatibility assets (`static/sf/sf.css`,
515
+
`static/sf/sf.js`) and versioned assets (`static/sf/sf.<version>.css`,
516
+
`static/sf/sf.<version>.js`).
517
+
509
518
## Acknowledgments
510
519
511
520
solverforge-ui builds on these excellent open-source projects:
0 commit comments