Skip to main content

Crate omena_resolver

Crate omena_resolver 

Source

Structs§

ModuleCanonicalIdV0
OmenaResolverBoundaryStateV0
Boundary-state witness for external-reference diagnostics.
OmenaResolverBoundarySummaryV0
OmenaResolverBundlerPathAliasMappingV0
OmenaResolverCanonicalUrlV0
Canonical URL returned by OmenaResolverV0::canonicalize.
OmenaResolverErrorV0
Resolver protocol error.
OmenaResolverLoadedSourceV0
Successful source load result for a canonical URL.
OmenaResolverModuleGraphModuleV0
OmenaResolverModuleGraphSummaryV0
OmenaResolverReferenceContextV0
Reference context for the shared omena resolver protocol.
OmenaResolverRuntimeModuleQueryV0
OmenaResolverRuntimeQueryBoundarySummaryV0
OmenaResolverSourceResolutionRuntimeEntryV0
OmenaResolverSourceResolutionRuntimeIndexV0
OmenaResolverSpecifierResolutionRuntimeEntryV0
OmenaResolverSpecifierResolutionRuntimeV0
OmenaResolverStyleModuleResolutionV0
OmenaResolverStyleModuleSnapshotV0
Snapshot-backed resolver that adapts today’s style module resolver to the RFC 0004 protocol without adding I/O to canonicalization.
OmenaResolverStylePackageManifestV0
OmenaResolverTsconfigPathMappingV0

Enums§

OmenaResolverBoundaryStateKindV0
Five-state external boundary model used by the SIF migration path.
OmenaResolverBoundaryTopV0
Abstract value top used when a boundary is not fully resolved.
OmenaResolverErrorKindV0
Error family for the shared resolver protocol.

Traits§

OmenaResolverV0
Shared resolver protocol for CLI, LSP, fixture, and query paths.

Functions§

canonicalize_module_id_v0
canonicalize_omena_resolver_style_identity_path
collect_omena_resolver_style_module_source_candidates
collect_omena_resolver_style_module_source_candidates_with_load_path_roots
collect_omena_resolver_style_module_source_candidates_with_path_mappings
collect_omena_resolver_style_module_source_candidates_with_tsconfig_paths
omena_resolver_boundary_state_for_unresolved_reference_v0
Surface the resolver-error channel for a reference whose canonical URL could not be canonicalized, then fold it onto the boundary lattice’s Unresolved state (#34).
omena_resolver_boundary_state_from_error_v0
query_omena_resolver_runtime_module
query_omena_resolver_source_expression
resolve_omena_resolver_style_module_source
resolve_omena_resolver_style_module_source_with_path_mappings
resolve_omena_resolver_style_module_source_with_tsconfig_paths
summarize_omena_resolver_boundary
summarize_omena_resolver_canonical_producer_signal
summarize_omena_resolver_module_graph_index
summarize_omena_resolver_query_fragments
summarize_omena_resolver_runtime_query_boundary
summarize_omena_resolver_source_resolution_runtime
summarize_omena_resolver_specifier_resolution_runtime
summarize_omena_resolver_specifier_resolution_runtime_with_path_mappings
summarize_omena_resolver_style_module_resolution
summarize_omena_resolver_style_module_resolution_with_load_path_roots
Resolve a style-module specifier, additionally trying each load_path_roots entry as a load-path root for path-shaped, non-./-relative, non-package specifiers (the dart-sass --load-path behavior). File-relative, alias, and bare-package routing are unchanged: the load-path candidates are appended last and only accepted when they exist in available_style_paths, so a genuinely missing module still flags and a real external package import still routes through the package resolver. (RFC-0007-I, #49)
summarize_omena_resolver_style_module_resolution_with_path_mappings
summarize_omena_resolver_style_module_resolution_with_tsconfig_paths