business-obligations-ui 0.5.0 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/dist/index.cjs +624 -428
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +29 -18
- package/dist/index.d.ts +29 -18
- package/dist/index.js +605 -409
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -111,7 +111,8 @@ that do apply, dimmed and with what would bring it in: items that are
|
|
|
111
111
|
not in `items` now, but would be if a detail that was left blank turned out a certain way. Each is a `ConditionalItem`,
|
|
112
112
|
`{ item, when: [{ field, values }] }`, and its card says what would bring it in ("Applies if number of employees: 1, 2,
|
|
113
113
|
3 …"). The package does not compute them; the playground does, from `analyzeInputs` and `evaluate`
|
|
114
|
-
(`conditionalItems` in `apps/web/src/lib/plan.ts`).
|
|
114
|
+
(`conditionalItems` in `apps/web/src/lib/plan.ts`). `LaunchList` takes the same list as `conditional` and shows it after the phases, in a section grouped by level, each with
|
|
115
|
+
what would bring it in and no checkbox. The list's filters apply to them too. Groups run from the most local level to the widest: city, county, state, federal.
|
|
115
116
|
|
|
116
117
|
## Bundle size
|
|
117
118
|
|