payload-live-preview 1.6.0 → 1.8.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/dist/adapters/astro/index.js +1 -1
- package/dist/adapters/astro/index.js.map +1 -1
- package/dist/adapters/astro/middleware-entry.js +1 -1
- package/dist/adapters/astro/middleware-entry.js.map +1 -1
- package/dist/adapters/nextjs/index.js +1 -1
- package/dist/adapters/nextjs/index.js.map +1 -1
- package/dist/adapters/nuxt/index.js +1 -1
- package/dist/adapters/nuxt/index.js.map +1 -1
- package/dist/adapters/sveltekit/index.js +1 -1
- package/dist/adapters/sveltekit/index.js.map +1 -1
- package/dist/core.cjs +1 -1
- package/dist/core.cjs.map +1 -1
- package/dist/core.d.cts +19 -0
- package/dist/core.d.ts +19 -0
- package/dist/core.js +1 -1
- package/dist/core.js.map +1 -1
- package/dist/index.cjs +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +19 -0
- package/dist/index.d.ts +19 -0
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/dist/index.d.cts
CHANGED
|
@@ -103,6 +103,17 @@ interface InspectionBindings {
|
|
|
103
103
|
* to update: a name here is a markup problem, a name absent from here and
|
|
104
104
|
* from `fieldNames` was never sent.
|
|
105
105
|
*/
|
|
106
|
+
/**
|
|
107
|
+
* Bound fields that some update since start carried no value for, so the
|
|
108
|
+
* binding kept whatever text it already had. Cumulative, like
|
|
109
|
+
* `orphanFields`, and the exact opposite of it: a binding with no value
|
|
110
|
+
* rather than a value with no binding.
|
|
111
|
+
*
|
|
112
|
+
* This is why a binding can stay stale while its siblings update. Without
|
|
113
|
+
* it the two cases are indistinguishable from the DOM, since neither
|
|
114
|
+
* leaves a trace.
|
|
115
|
+
*/
|
|
116
|
+
readonly absentFields: readonly string[];
|
|
106
117
|
readonly orphanFields: readonly string[];
|
|
107
118
|
/** Whether `scopeBindingsByOwner` is active. */
|
|
108
119
|
readonly ownerScoped: boolean;
|
|
@@ -126,6 +137,14 @@ interface InspectionScheduler {
|
|
|
126
137
|
/** Stats of the most recent flush, or `undefined` if none has run. */
|
|
127
138
|
readonly lastFlush: {
|
|
128
139
|
readonly applied: number;
|
|
140
|
+
/**
|
|
141
|
+
* Field names the flush applied, in application order.
|
|
142
|
+
*
|
|
143
|
+
* `applied` is a count, and a count cannot separate "this binding was
|
|
144
|
+
* written" from "this binding was never scheduled" — a stale binding
|
|
145
|
+
* next to a non-zero count is consistent with both. The names can.
|
|
146
|
+
*/
|
|
147
|
+
readonly appliedFields: readonly string[];
|
|
129
148
|
readonly deferred: number;
|
|
130
149
|
readonly durationMs: number;
|
|
131
150
|
} | undefined;
|
package/dist/index.d.ts
CHANGED
|
@@ -103,6 +103,17 @@ interface InspectionBindings {
|
|
|
103
103
|
* to update: a name here is a markup problem, a name absent from here and
|
|
104
104
|
* from `fieldNames` was never sent.
|
|
105
105
|
*/
|
|
106
|
+
/**
|
|
107
|
+
* Bound fields that some update since start carried no value for, so the
|
|
108
|
+
* binding kept whatever text it already had. Cumulative, like
|
|
109
|
+
* `orphanFields`, and the exact opposite of it: a binding with no value
|
|
110
|
+
* rather than a value with no binding.
|
|
111
|
+
*
|
|
112
|
+
* This is why a binding can stay stale while its siblings update. Without
|
|
113
|
+
* it the two cases are indistinguishable from the DOM, since neither
|
|
114
|
+
* leaves a trace.
|
|
115
|
+
*/
|
|
116
|
+
readonly absentFields: readonly string[];
|
|
106
117
|
readonly orphanFields: readonly string[];
|
|
107
118
|
/** Whether `scopeBindingsByOwner` is active. */
|
|
108
119
|
readonly ownerScoped: boolean;
|
|
@@ -126,6 +137,14 @@ interface InspectionScheduler {
|
|
|
126
137
|
/** Stats of the most recent flush, or `undefined` if none has run. */
|
|
127
138
|
readonly lastFlush: {
|
|
128
139
|
readonly applied: number;
|
|
140
|
+
/**
|
|
141
|
+
* Field names the flush applied, in application order.
|
|
142
|
+
*
|
|
143
|
+
* `applied` is a count, and a count cannot separate "this binding was
|
|
144
|
+
* written" from "this binding was never scheduled" — a stale binding
|
|
145
|
+
* next to a non-zero count is consistent with both. The names can.
|
|
146
|
+
*/
|
|
147
|
+
readonly appliedFields: readonly string[];
|
|
129
148
|
readonly deferred: number;
|
|
130
149
|
readonly durationMs: number;
|
|
131
150
|
} | undefined;
|