Skip to content

BUG - Context hard-coded to latest #23

Description

@RaggedStaff

Getting an issue with connector version v1.0.0-beta.2

Two files in node_modules hardcode releases/latest/:

  • node_modules/@datafoodconsortium/connector/lib/context.js — prefix definitions
  • node_modules/@datafoodconsortium/connector/lib/ConnectorFactory.js — the createFromType() switch that matches expanded type URIs

So when an incoming payload references version-pinned paths (e.g. releases/1.16.0/)., the connector fetches it, expands dfc-b:Order to .../1.16.0/..., and the factory doesn't recognize it, then silently drops it → "Order missing".

I think we need to ensure the v1 connector has contexts pinned to v1.16.0

Does that make sesnse @lecoqlibre

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions