@sifa.id I'm using your sdk specifically for your schemas/types when reading sifa data from my PDS. When using ProfilePositionRecordSchema it specifies skills as strongRefSchema. That schema defines cid as required with cidSchema. The lexicon, however, has cid as optional. My records have no cid.
Post
Maybe I'm using it incorrectly? For now, I'm extending ProfilePositionRecordSchema and overriding cid, making it optional.
0 reposts0 likes
Fixed and published in @singi-labs/sifa-sdk 0.12.38. Same release adds isPrimary, which the lexicon has yet the schema was silently stripping... Issue and audit of the other refs: github.com/singi-labs/sifa-sdk/issues/383
github.comProfilePositionRecordSchema.skills requires a cid the lexicon never defines · Issue #383 · singi-labs/sifa-sdkReported by @bljohnson.dev, reading id.sifa.* records straight from a PDS with the SDK's schemas. Problem src/schemas/profile-position.ts:31 validates skills entries with strongRefSchema, which req...
There was a docs gap on our side too: the PDS-read path never said the root subpath ships a Zod schema per record, or that not every ref carries a cid. Fixed: docs.sifa.id/docs/integrate-profiles Keep 'm coming. Third-party reads are exactly what these schemas are for 💪
docs.sifa.idShow Sifa profiles in your appRead a person's professional headline, current role, employer, and skills from their Sifa profile, and render it in your own app. Public data, no Sifa account, no API key.