Fix MSW endpoint mismatch: /metadata/object → /meta/object

[Copilot]

CI tests failing because MSW handlers intercepted /api/v1/metadata/object/:name while ObjectStack client calls /api/v1/meta/object/:name, causing unhandled fetch requests.

Changes

• Test MSW handlers - Updated endpoint paths in:

  • packages/plugin-grid/src/ObjectGrid.msw.test.tsx
  • packages/plugin-form/src/ObjectForm.msw.test.tsx
  • packages/plugin-calendar/src/ObjectCalendar.msw.test.tsx
  • .storybook/msw-browser.ts

• Console mock server - Added missing /meta/object/:name handler to apps/console/src/mocks/server.ts (already had /meta/objects/:name plural variant)

Before:

http.get(`${BASE_URL}/api/v1/metadata/object/contact`, () => { ... })

After:

http.get(`${BASE_URL}/api/v1/meta/object/contact`, () => { ... })

Original prompt

引用: https://github.com/objectstack-ai/objectui/actions/runs/21591319949/job/62211927313#step:8:1

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectui	Ready	Preview, Comment	Feb 2, 2026 1:45pm
objectui-components	Ready	Preview, Comment	Feb 2, 2026 1:45pm
objectui-crm-app	Error		Feb 2, 2026 1:45pm

[xuyushun441-sys]

@copilot 继续

[Copilot]

Pull request overview

This PR aligns MSW mock endpoints with the ObjectStack client’s actual /api/v1/meta/object/:name usage so that tests and Storybook no longer generate unhandled request errors, and adds the missing console mock handler for the singular meta-object route.

Changes:

• Updated MSW handlers in grid, form, and calendar plugin tests from /api/v1/metadata/object/... to /api/v1/meta/object/... to match the ObjectStack client.
• Adjusted Storybook’s browser MSW configuration to use /api/v1/meta/object/:objectName for metadata requests.
• Extended the console mock server to handle the singular /meta/object/:objectName endpoint in addition to existing plural/legacy variants.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/plugin-grid/src/ObjectGrid.msw.test.tsx	Updates the grid test’s schema fetch handler to /api/v1/meta/object/contact, matching the adapter’s expected endpoint.
packages/plugin-form/src/ObjectForm.msw.test.tsx	Updates the form test’s generic schema handler to /api/v1/meta/object/:name, avoiding unhandled MSW requests during form schema loading.
packages/plugin-calendar/src/ObjectCalendar.msw.test.tsx	Points the calendar test’s metadata query to /api/v1/meta/object/events to align with the ObjectStack client.
apps/console/src/mocks/server.ts	Adds a new /meta/object/:objectName handler (parallel to the existing /metadata/object/:objectName handler) so the console mock server supports the singular meta-object route used by the client.
.storybook/msw-browser.ts	Switches the Storybook metadata handler to /api/v1/meta/object/:objectName, ensuring Storybook stories use the same meta-object path as the runtime client.

[Copilot]

The new handler for ${baseUrl}/meta/object/:objectName duplicates almost the same logic as the existing ${baseUrl}/metadata/object/:objectName handler below (logging, getMetaItem call, payload unwrapping, and error handling). To reduce maintenance overhead and risk of future drift between these endpoints, consider extracting a shared helper (e.g., a function that takes the path or a common handler factory) and reuse it for both routes.