As a first-time poster in the Palantir Community, I would like to initiate a discussion around OSDK v2 TypeScript compilation and property binding experience in Code Repositories. While working on an AIP Chatbot Agent backed by TypeScript functions querying an Ontology Object Set (UnnirInventoryBalance), I encountered a subtle issue where an internal property mapping mismatch resulted in runtime zero-count/null returns rather than triggering compile-time diagnostics or highlighting errors in the Problems tab.
Given Palantir Foundry’s unified “all-under-one-roof” architecture—where the Ontology, Code Repositories, and AIP Studio coexist within the same tenant—it would be immensely beneficial if the TypeScript compiler or static code analysis could flag display-name vs API-name mismatches or unmapped property keys directly during the build phase. Relying purely on runtime execution to uncover empty schema payloads can slow down debugging. I would love to hear how the community and product teams handle strict compile-time property assertions or if tighter, automated schema validation checks are planned for future OSDK v2 releases!