Enum cedar_policy_core::entities::JsonSerializationError

pub enum JsonSerializationError {
    Serde(Error),
    ExtnCall0Arguments {
        func: Name,
    },
    ExtnCall2OrMoreArguments {
        func: Name,
    },
    ReservedKey {
        key: SmolStr,
    },
    UnexpectedRestrictedExprKind {
        kind: ExprKind,
    },
    Residual {
        residual: Expr,
    },
}

Errors thrown during serialization to JSON

Variants

Serde(Error)

Error thrown by serde_json

ExtnCall0Arguments

Extension-function calls with 0 arguments are not currently supported in our JSON format.

Fields

func: Name

Name of the function which was called with 0 arguments

ExtnCall2OrMoreArguments

Extension-function calls with 2 or more arguments are not currently supported in our JSON format.

Fields

func: Name

Name of the function which was called with 2 or more arguments

ReservedKey

Encountered a Record which can’t be serialized to JSON because it contains a key which is reserved as a JSON escape.

Fields

key: SmolStr

Reserved key which was used by the Record

UnexpectedRestrictedExprKind

Encountered an ExprKind which we didn’t expect. Either a case is missing in CedarValueJson::from_expr(), or an internal invariant was violated and there is a non-restricted expression in RestrictedExpr

Fields

kind: ExprKind

ExprKind which we didn’t expect to find

Residual

Encountered a (partial-evaluation) residual which can’t be encoded in JSON

Fields

residual: Expr

Residual which can’t be encoded in JSON

Trait Implementations

impl Debug for JsonSerializationError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Diagnostic for JsonSerializationError

fn help(&self) -> Option<Box<dyn Display + '_>>

Additional help text related to this Diagnostic. Do you have any advice for the poor soul who’s just run into this issue?

fn code<'a>(&'a self) -> Option<Box<dyn Display + 'a>>

Unique diagnostic code that can be used to look up more information about this Diagnostic. Ideally also globally unique, and documented in the toplevel crate’s documentation for easy searching. Rust path format (foo::bar::baz) is recommended, but more classic codes like E0123 or enums will work just fine.

fn severity(&self) -> Option<Severity>

Diagnostic severity. This may be used by ReportHandlers to change the display format of this diagnostic.

fn url<'a>(&'a self) -> Option<Box<dyn Display + 'a>>

URL to visit for a more detailed explanation/help about this Diagnostic.

fn source_code(&self) -> Option<&dyn SourceCode>

Source code to apply this Diagnostic’s Diagnostic::labels to.

fn labels(&self) -> Option<Box<dyn Iterator<Item = LabeledSpan> + '_>>

Labels to apply to this Diagnostic’s Diagnostic::source_code

fn related<'a>( &'a self, ) -> Option<Box<dyn Iterator<Item = &'a dyn Diagnostic> + 'a>>

Additional related Diagnostics.

fn diagnostic_source(&self) -> Option<&dyn Diagnostic>

The cause of the error.

impl Display for JsonSerializationError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for JsonSerializationError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0: use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0: replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<Error> for JsonSerializationError

fn from(source: Error) -> Self

Converts to this type from the input type.

impl From<JsonSerializationError> for EntitiesError

fn from(source: JsonSerializationError) -> Self

Converts to this type from the input type.