Type Members

1.  case class AdditionalPropertyContext(element: AmfObject, baseUnit: BaseUnit, documentDefinition: DocumentDefinition, alsConfigurationState: ALSConfigurationState) extends Product with Serializable
2.  trait AdditionalPropertyPlugin extends AnyRef
3.  case class GuessedBranch(elements: Seq[GuessedElement]) extends Product with Serializable

   A single traversal path from outermost to innermost through the schema.

   A single traversal path from outermost to innermost through the schema.

   elements

   the sequence of (instance, definition) pairs from outermost to innermost

4.  case class GuessedElement(shape: Shape, definition: Shape) extends Product with Serializable

   A single element in the guessing traversal: pairs an instance shape with its schema definition.

   A single element in the guessing traversal: pairs an instance shape with its schema definition.

   shape

   the shape representing the instance element in the document

   definition

   the schema definition shape that describes the instance element

5.  case class GuessedShapeResult(branches: Seq[GuessedBranch]) extends Product with Serializable

   Result of the guessing game: contains all viable branches of guessed shapes.

   Result of the guessing game: contains all viable branches of guessed shapes.

   branches

   all viable traversal paths through the schema

6.  class SchemaDefinitionResolver extends AnyRef

   Centralized, lazily-populated cache for resolving JSON Schema definitions.

   Centralized, lazily-populated cache for resolving JSON Schema definitions.

   When AMF parses a JsonLDInstanceDocument it annotates each object with a SourceSchemaDef linking it to its schema definition. However, AMF often cannot disambiguate behind oneOf/anyOf, leaving many objects without this annotation.

   This resolver provides two resolution strategies sharing a single object-level cache:

   • Branch-guided (resolve(element, stack, astPartBranch)): Navigates the schema tree following the AST branch and caches each object's definition as it drills through the schema tree following the AST branch. Use this from completions and hover where cursor position matters.
   • Stack-based (resolve(element, stack)): Walks the ancestor stack using object field / ID matching and caches intermediates. Use this from visitors and other position-independent consumers.

   Because both paths write to the same cache, a branch-guided resolution of [current, a, b, c, d, root] will cache definitions for every intermediate object, so a subsequent query for [sub-current, current, …] resolves in O(1) from current.