diff --git a/apps/e2e/src/e2e.test.ts b/apps/e2e/src/e2e.test.ts index 3903c357..ccbfa586 100644 --- a/apps/e2e/src/e2e.test.ts +++ b/apps/e2e/src/e2e.test.ts @@ -11,7 +11,7 @@ const ky = defaultKy.extend({ // Disable automatic retries for testing. retry: 0, - // Some tests expect HTTP errors, so handle them manually. + // Some tests expect HTTP errors, so handle them manually instead of throwing. throwHttpErrors: false }) diff --git a/apps/e2e/src/env.ts b/apps/e2e/src/env.ts index 53087f2f..68a3cbf6 100644 --- a/apps/e2e/src/env.ts +++ b/apps/e2e/src/env.ts @@ -5,12 +5,9 @@ import { z } from 'zod' // TODO: derive AGENTIC_API_BASE_URL and AGENTIC_GATEWAY_BASE_URL based on // environment. +// TODO: use `@agentic/platform-hono` base env like other services export const envSchema = z.object({ - ENVIRONMENT: z - .enum(['development', 'test', 'production']) - .default('development'), - AGENTIC_API_BASE_URL: z.string().url().optional(), AGENTIC_API_ACCESS_TOKEN: z.string().nonempty(), @@ -25,6 +22,3 @@ export const envSchema = z.object({ export const env = parseZodSchema(envSchema, process.env, { error: 'Invalid environment variables' }) - -export const isDev = env.ENVIRONMENT === 'development' -export const isProd = env.ENVIRONMENT === 'production' diff --git a/readme.md b/readme.md index bb9fd5ac..b921ce1d 100644 --- a/readme.md +++ b/readme.md @@ -9,9 +9,9 @@ - **webapp** - end-to-end working examples - - raw - openapi - mcp + - raw - stripe - re-add coupons - declarative json-based pricing @@ -37,8 +37,6 @@ - add username / team name blacklist - admin, internal, mcp, sse, etc - **API gateway** - - share hono middleware and utils across apps/api and apps/gateway - - or combine these together? ehhhh - MCP server vs REST gateway on public and internal sides - **REST**: `GET/POST gateway.agentic.so/deploymentIdentifier/toolName` - => MCP: `MCPClient.callTool` with JSON body parameters @@ -52,8 +50,9 @@ - add support for custom headers on responses - how to handle binary bodies and responses? - signed requests -- revisit deployment identifiers so possibly be URL-friendly? -- move validators package into platform-types? +- public identifiers and validators + - revisit deployment identifiers so possibly be URL-friendly? + - move validators package into platform-types? - force toolPath to be non-empty except for `raw`? - will remove ambiguity from `username/` - make namespace optional? and require `@` prefix if so? like npm packages