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: docs/next-steps.md
+1-9Lines changed: 1 addition & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,15 +26,7 @@ Focused follow-up work for `@knighted/develop`.
26
26
- Suggested implementation prompt:
27
27
- "Evaluate and optionally optimize @knighted/develop GitHub file upsert behavior. Compare metadata-first preflight GET+PUT against optimistic PUT with retry-on-missing-sha for existing files. Keep current reliability guarantees and avoid reintroducing noisy false-positive failures. If implementing a hybrid/configurable strategy, keep defaults conservative, update docs, and validate with npm run lint plus targeted Playwright PR drawer flows."
- Delete code paths that preserve or translate legacy single-component/single-styles storage and sync behavior from before the multitab update.
31
-
- Remove backward-compatibility shims, fallback field reads, and migration glue tied to old `componentFilePath`/`stylesFilePath`-style assumptions when equivalent tab-derived data exists.
32
-
- Favor one canonical tab-first data contract across local storage, IndexedDB workspace records, PR sync metadata, and commit target derivation.
33
-
- Accept breaking changes for old locally stored app state to simplify maintenance and reduce branching logic.
34
-
- Suggested implementation prompt:
35
-
- "Remove backwards-compatibility code in @knighted/develop that supports pre-multitab component/styles storage/sync behavior. Standardize on the current tab-derived schema only, delete legacy field fallbacks and migration helpers, and update tests/docs to match the simplified contract. Validate with npm run lint and targeted Playwright suites for workspace tabs + PR drawer flows."
36
-
37
-
6.**Promise handling conventions (consistency of intent)**
29
+
5.**Promise handling conventions (consistency of intent)**
38
30
- Define a project default: use `async`/`await` with `try`/`catch` for most async control flow.
39
31
- Keep Promise chains where they better express intent (for example, fire-and-forget paths with explicit `.catch()` to avoid unhandled rejections, or concise pass-through composition).
40
32
- Document this as an intent-first rule so mixed syntax is acceptable only when deliberate and easy to reason about.
0 commit comments