Skip to content
This repository was archived by the owner on Jan 29, 2026. It is now read-only.

LA-224 AI fitting step 8 - Adobe types, 2nd phase#57

Open
Edwin-van-der-Klaauw wants to merge 3 commits into
LA-224_AI-fitting7-adobe-typesfrom
LA-224_AI-fitting8-adobe-types2
Open

LA-224 AI fitting step 8 - Adobe types, 2nd phase#57
Edwin-van-der-Klaauw wants to merge 3 commits into
LA-224_AI-fitting7-adobe-typesfrom
LA-224_AI-fitting8-adobe-types2

Conversation

@Edwin-van-der-Klaauw

Copy link
Copy Markdown
Contributor

Rather than linking to remote git repo, npm install the types-for-adobe to make the same as done for the uxp types.
Only invoke the types/*.d.ts files and let them refer to the desired DOM version.
Make the types files more complete.
Add a types file for the scripting API that is extended by the SC plugins for InDesign.
Prepare the codebase for the jsCheck option, but I could not solve all, so left it false for now.
Because quite some InDesign types are "number | string" there is a need to cast them to Number(...) before using.

…for-adobe to make the same as done for the uxp types. Only invoke the types/*.d.ts files and let them refer to the desired DOM version. Make the types files more complete. Also add a types file for the scripting API that is extended by the SC plugins for InDesign. Prepare the codebase for the jsCheck option, but I could not solve all, so left it false for now. Because quite some InDesign types are "number | string" there is a need to cast them to Number(...) before using.

@tpiwoodwing tpiwoodwing left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants