@outbuild-company/schedule-core 1.17.0-p6.2 → 1.17.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 +0 -35
- package/dist/cdn/schedule-core.global.js +1 -1
- package/dist/cdn/schedule-core.global.js.map +1 -1
- package/dist/index.cjs +501 -7332
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +1145 -1622
- package/dist/index.d.ts +1145 -1622
- package/dist/index.js +501 -7319
- package/dist/index.js.map +1 -1
- package/package.json +2 -5
package/README.md
CHANGED
|
@@ -82,41 +82,6 @@ The library accepts backend-shaped schedule data, normalizes it internally and
|
|
|
82
82
|
returns a ready instance. A successful mutation updates core state and returns
|
|
83
83
|
the complete `ChangeSet`; a rejected mutation leaves state untouched.
|
|
84
84
|
|
|
85
|
-
## P6 Schedule defaults and readiness
|
|
86
|
-
|
|
87
|
-
`core.p6.getDefaultSettings()` returns a fresh, detached settings value on every call. The Outbuild defaults are:
|
|
88
|
-
|
|
89
|
-
```ts
|
|
90
|
-
{
|
|
91
|
-
dataDate: null,
|
|
92
|
-
outOfSequencePolicy: 'retained_logic',
|
|
93
|
-
dependencyReference: 'correlative_id',
|
|
94
|
-
useExpectedFinishDates: true,
|
|
95
|
-
startToStartLagBasis: 'early_start',
|
|
96
|
-
relationshipLagCalendar: 'predecessor',
|
|
97
|
-
totalFloatMethod: 'finish_float',
|
|
98
|
-
criticalActivityMethod: 'total_float',
|
|
99
|
-
criticalFloatThresholdHours: 0,
|
|
100
|
-
makeOpenEndedActivitiesCritical: false,
|
|
101
|
-
externalRelationshipPolicy: 'SD_Both',
|
|
102
|
-
calculateFloatBasedOn: 'each_project',
|
|
103
|
-
setDataDateAndPlannedStartToForecastStart: false,
|
|
104
|
-
projectMustFinishBy: null,
|
|
105
|
-
projectForecastStart: null,
|
|
106
|
-
multipleFloatPaths: {
|
|
107
|
-
enabled: false,
|
|
108
|
-
limitEnabled: false,
|
|
109
|
-
maximum: 10,
|
|
110
|
-
useTotalFloat: true,
|
|
111
|
-
endingActivityId: null
|
|
112
|
-
}
|
|
113
|
-
}
|
|
114
|
-
```
|
|
115
|
-
|
|
116
|
-
`core.p6.getScheduleReadiness(patch?)` evaluates a patch without changing settings, project state, activities, links, revision, dirty state, or history. It checks P6 capability, imported external relationships, patch validity, effective Forecast Start, and Data Date before reporting readiness.
|
|
117
|
-
|
|
118
|
-
The readiness query performs no activity or link scan. `schedule()` throws `P6CapabilityError` with the same blocker code for blocked results.
|
|
119
|
-
|
|
120
85
|
## One engine, two public entry points
|
|
121
86
|
|
|
122
87
|
| Consumer | Entry point |
|