PaginationNotSyncedError
Thrown when a pagination helper that needs state.lastPage is called
before PaginationService.paginate() has ever synced a value.
Examples: NgQubeeService.lastPage(), NgQubeeService.totalPages().
Safe-for-templates predicates (isLastPage, hasNextPage, etc.) do not
throw and return conservative defaults instead.
Constructor
Section titled “Constructor”new PaginationNotSyncedError(action: string)| Parameter | Type | Description |
|---|---|---|
action |
string |
Short imperative describing what the caller was trying to do (e.g. “navigate to last page”, “read totalPages”). Surfaced in the error message so the cause is obvious at the call site. |
Properties
Section titled “Properties”| Property | Type | Description |
|---|---|---|
cause |
unknown |
— |
code |
QubeeErrorCode |
Machine-readable identifier for this failure. |
context |
Record<string, unknown> |
The values that produced the error, when they aid diagnosis. |
message |
string |
— |
name |
string |
— |
stack |
string |
— |
stackTraceLimit |
number |
The Error.stackTraceLimit property specifies the number of stack frames collected by a stack trace (whether generated by new Error().stack or Error.captureStackTrace(obj)). The default value is 10 but may be set to any valid JavaScript number. Changes will affect any stack trace captured after the value has been changed. If set to a non-number value, or set to a negative number, stack traces will not capture any frames. |
Methods
Section titled “Methods”captureStackTrace()
Section titled “captureStackTrace()”captureStackTrace(targetObject: object, constructorOpt?: Function): voidCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};Error.captureStackTrace(myObject);myObject.stack; // Similar to `new Error().stack`The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() { b();}
function b() { c();}
function c() { // Create an error without stack trace to avoid calculating the stack trace twice. const { stackTraceLimit } = Error; Error.stackTraceLimit = 0; const error = new Error(); Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace throw error;}
a();| Parameter | Type | Description |
|---|---|---|
targetObject |
object |
— |
constructorOpt |
Function |
— |
prepareStackTrace()
Section titled “prepareStackTrace()”prepareStackTrace(err: Error, stackTraces: CallSite[]): any| Parameter | Type | Description |
|---|---|---|
err |
Error |
— |
stackTraces |
CallSite[] |
— |
