LF-5362: Upgrade to @datafoodconsortium/connector v2#4235
Draft
SayakaOno wants to merge 5 commits into
Draft
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
…ory and makeMarketDirectoryInfo function" This reverts commit 1741f56.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Upgrade
@datafoodconsortium/connectortov2.0.0-beta.2(CHANGELOG) and restores existing DFC API functionality under the new version.Breaking changes addressed
Enterprise→Organizationin the adapter and all testsdfc-b:hasAddresscountryfield now requires aSKOSConceptobject instead of a plain string URINew in this PR
Content-Type: application/ld+json; profile="dfc-v2"response header on both DFC endpointsGET /dfc/enterprises/response wrapped inldp:Containerfor DFC v2 complianceTaxonomy file
The v2 release taxonomy is structurally incompatible with the connector's
importThesaurus(usesbroaderonly, noConceptScheme/hasTopConcept). As a workaround, the v1 taxonomy structure is retained with the URI prefix updated tohttp://w3id.org/dfc/taxonomies/v2.0.0/productTypes.rdf#.Other changes
x.comdfc-b:hasAddress,dfc-b:hasMainContact, etc.) are now serialized as plain URI strings instead of{"@id": "..."}objects — this is v2 connector behaviour, semantically equivalent per JSON-LD specJira link: https://lite-farm.atlassian.net/browse/LF-5362
Type of change
How Has This Been Tested?
Checklist:
pnpm i18nto help with this)