Skip to content

fix: update @constructive-io/sdk references to @constructive-io/node#83

Open
pyramation wants to merge 1 commit intomainfrom
feat/update-sdk-references
Open

fix: update @constructive-io/sdk references to @constructive-io/node#83
pyramation wants to merge 1 commit intomainfrom
feat/update-sdk-references

Conversation

@pyramation
Copy link
Copy Markdown
Contributor

Summary

Updates metadata, descriptions, and compatibility lines across 5 skill files to reference @constructive-io/node instead of the older @constructive-io/sdk package. This aligns the public skills repo with the broader migration happening in constructive-sdk-agentic-flow#22, which rewrites the agentic flow to use @constructive-io/node with TypeScript blueprints.

Files changed:

  • constructive-graphql/SKILL.md — "Design DB" flow step
  • constructive-safegres/SKILL.md — compatibility frontmatter
  • constructive/SKILL.md — Services & Schemas description
  • constructive/references/services-schemas.md — description, compatibility, heading
  • constructive/references/services-schemas-entity-fields.md — header

What was NOT changed: The import { createClient } from '@constructive-io/sdk' code examples inside services-schemas.md were intentionally left as-is, since they reflect generated ORM patterns that may still use that import path.

Review & Testing Checklist for Human

  • Verify @constructive-io/node exposes the same service management APIs referenced in services-schemas.md (e.g., sdk.api.create, sdk.domain.create, sdk.apiSchema.create). If the node package has different import paths or API shapes, the code examples in services-schemas.md may also need updating.
  • Check whether the code examples in services-schemas.md should also be updated — the metadata now says @constructive-io/node but the inline code still imports from @constructive-io/sdk. Confirm whether this inconsistency is acceptable or if the examples should be migrated too.
  • Grep for any remaining @constructive-io/sdk references across the skills repo that should also be updated (e.g., graphile-search/references/codegen-sdk-queries.md, constructive-graphql/references/codegen-orm-output.md).

Notes

  • Companion PR: constructive-sdk-agentic-flow#22 — the main audit fix that rewrites the agentic flow to use TypeScript blueprints with @constructive-io/node.
  • The remaining @constructive-io/sdk references in codegen output docs (codegen-orm-output.md) were left untouched since those describe what the code generator actually produces, which may still emit @constructive-io/sdk imports.

Link to Devin session: https://app.devin.ai/sessions/930052e50e294d428ba075050525e0f8
Requested by: @pyramation

- constructive-graphql SKILL.md: update 'Design DB' step to reference @constructive-io/node
- constructive-safegres SKILL.md: update compatibility line
- constructive SKILL.md: update Services & Schemas description
- services-schemas.md: update description and compatibility metadata
- services-schemas-entity-fields.md: update header reference

Note: Code examples in services-schemas.md that use 'createClient from @constructive-io/sdk'
are left as-is since they reflect generated ORM patterns that may still use that import path.
@devin-ai-integration
Copy link
Copy Markdown

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant