Analyzer::Specification::OData
Inherits Analyzer::Specification::SpecificationEngine < Analyzer < FileHelper < Reference < Object
OData CSDL ($metadata) describes a service's entity sets,
singletons, and function/action imports. We turn each of those
into the standard URL conventions a real client would call. The
base path is left implicit (/) because CSDL doesn't carry the
service root — downstream consumers prefix it from their own
context.
Constants
EDM_PRIMITIVE_BODY_TYPES = {"Edm.String" => "string", "Edm.Boolean" => "boolean", "Edm.Int16" => "int", "Edm.Int32" => "int", "Edm.Int64" => "int", "Edm.Decimal" => "number", "Edm.Double" => "number", "Edm.Single" => "number", "Edm.Byte" => "int", "Edm.SByte" => "int", "Edm.Guid" => "string", "Edm.DateTime" => "string", "Edm.Date" => "string", "Edm.TimeOfDay" => "string", "Edm.DateTimeOffset" => "string", "Edm.Duration" => "string", "Edm.Binary" => "string"}
Class methods
tech_name
SourceInstance methods
analyze
Sourcetech
Instance-side view of the same declaration. The per-file rescues live on
this base class, which has no way to name the analyzer that is running
inside them, so a skipped file could not be attributed to a tech.
Deriving it from analyzer_for keeps the name written exactly once.