Skip to content

Comments

Move camera API to platform APIs#3921

Closed
chadwcarlson wants to merge 33 commits into2026-04-rcfrom
2026-01
Closed

Move camera API to platform APIs#3921
chadwcarlson wants to merge 33 commits into2026-04-rcfrom
2026-01

Conversation

@chadwcarlson
Copy link

Background

(Provide a link to any relevant issues AND provide a TLDR of the issue in this pull request)

Solution

(Describe your solution, why this approach was chosen, and what the alternatives/impacts may be)

🎩

  • ...

Checklist

  • I have 🎩'd these changes
  • I have updated relevant documentation

andy-chhuon and others added 30 commits January 29, 2026 10:14
The issue_comment trigger was lost when merging from 2025-10. The snapit
job checks for issue_comment events but the workflow wasn't configured
to trigger on them.

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
…3781)

Introduces StandardRenderingExtensionApi that extends StandardApi with
resourcePicker and picker APIs. All rendering extension APIs now extend
this instead of StandardApi directly, giving them access to picker APIs.

This keeps StandardApi minimal for non-rendering extensions like
admin.app.tools.data that have no use for picker dialogs.

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* Add and improve descriptions for Target APIs

Further improvements to descriptions

Best practices, limitations, and further description improvements

Linting

Cross-references to docs

Revisions

Further description improvements

Intents API content revisions

Resource picker and Picker revisions

Description feedback from Steve

Revamp limitations + best practices

Further revisions

Revise newly added descriptions

* Fix type
…path-2026-01

Chore/update shopify dev asset path 2026 01
…field-docs

[2026-01] Update metafield docs
…-docs-2026-01

chore: update all paths in build-docs scripts 2026-01
Co-authored-by: Cursor <cursoragent@cursor.com>
[Target APIs content]: Examples and descriptions for 2026-01
- Add shared type-resolver module for parsing TypeScript types
- Detect @Private JSDoc tags on type definitions and extension targets
- Exclude @Private components (e.g., Chat) from general targets
- Exclude @Private extension targets from output
- Still allow @Private components in explicit AllowedComponents<> targets
- Handle Exclude<> types correctly for component filtering
- Add test coverage for @Private exclusion logic
Add support for RunnableExtension targets (like should-render and
address-autocomplete) which don't render UI components but should
still be documented. These targets now appear with components: []
and their associated APIs.
…hopify-dev-2026-01

chore: update all paths in build-docs fast/watch scripts 2026-01
* Make API headings consistent for Admin UI

* Make API headings consistent for POS UI

* Minor fixes

* Rename 'Methods' to 'Properties' in API headings and descriptions

Co-authored-by: Cursor <cursoragent@cursor.com>

* Remove 'methods' from API description text, use 'properties' instead

Co-authored-by: Cursor <cursoragent@cursor.com>

* Revert title for applyMetafieldChange back to original name

Co-authored-by: Cursor <cursoragent@cursor.com>

* Revert title for picker back to original name

Co-authored-by: Cursor <cursoragent@cursor.com>

* Revert specific function/method titles back to original names

Co-authored-by: Cursor <cursoragent@cursor.com>

* Revert changes to using-polaris-web-components.doc.ts files

Co-authored-by: Cursor <cursoragent@cursor.com>

* Fix admin.app.tools.data description

* Add more context re: admin.app.tools.data target

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
…heckout-metafield-read

[2026-01] Add deprecation warning to checkout metafield read API
Copy link
Author

chadwcarlson commented Feb 18, 2026

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.

9 participants