Struct VariablePresentationHint 

pub struct VariablePresentationHint {
    pub kind: Option<VariablePresentationHintKind>,
    pub attributes: Option<Vec<VariablePresentationHintAttributes>>,
    pub visibility: Option<VariablePresentationHintVisibility>,
    pub lazy: Option<bool>,
}

Fields

kind: Option<VariablePresentationHintKind>

The kind of variable. Before introducing additional values, try to use the listed values. Values: ‘property’: Indicates that the object is a property. ‘method’: Indicates that the object is a method. ‘class’: Indicates that the object is a class. ‘data’: Indicates that the object is data. ‘event’: Indicates that the object is an event. ‘baseClass’: Indicates that the object is a base class. ‘innerClass’: Indicates that the object is an inner class. ‘interface’: Indicates that the object is an interface. ‘mostDerivedClass’: Indicates that the object is the most derived class. ‘virtual’: Indicates that the object is virtual, that means it is a synthetic object introduced by the adapter for rendering purposes, e.g. an index range for large arrays. ‘dataBreakpoint’: Deprecated: Indicates that a data breakpoint is registered for the object. The hasDataBreakpoint attribute should generally be used instead. etc.

attributes: Option<Vec<VariablePresentationHintAttributes>>

Set of attributes represented as an array of Strings. Before introducing additional values, try to use the listed values. Values: ‘static’: Indicates that the object is static. ‘constant’: Indicates that the object is a constant. ‘readOnly’: Indicates that the object is read only. ‘rawString’: Indicates that the object is a raw String. ‘hasObjectId’: Indicates that the object can have an Object ID created for it. ‘canHaveObjectId’: Indicates that the object has an Object ID associated with it. ‘hasSideEffects’: Indicates that the evaluation had side effects. ‘hasDataBreakpoint’: Indicates that the object has its value tracked by a data breakpoint. etc.

visibility: Option<VariablePresentationHintVisibility>

Visibility of variable. Before introducing additional values, try to use the listed values. Values: ‘public’, ‘private’, ‘protected’, ‘internal’, ‘final’, etc.

lazy: Option<bool>

If true, clients can present the variable with a UI that supports a specific gesture to trigger its evaluation. This mechanism can be used for properties that require executing code when retrieving their value and where the code execution can be expensive and/or produce side-effects. A typical example are properties based on a getter function. Please note that in addition to the lazy flag, the variable’s variablesReference is expected to refer to a variable that will provide the value through another variable request.

Trait Implementations

impl Clone for VariablePresentationHint

fn clone(&self) -> VariablePresentationHint

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for VariablePresentationHint

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

Formats the value using the given formatter.

impl Default for VariablePresentationHint

fn default() -> VariablePresentationHint

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for VariablePresentationHint

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for VariablePresentationHint

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.