Skip to content

Commit c72c3ad

Browse files
committed
fix: allow empty fieldNameSuffix in hashing mapper schema (#18367)
1 parent 10389cc commit c72c3ad

File tree

1 file changed

+8
-2
lines changed
  • airbyte-webapp/src/components/connection/ConnectionForm/schemas

1 file changed

+8
-2
lines changed

airbyte-webapp/src/components/connection/ConnectionForm/schemas/mapperSchema.ts

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,16 @@ import {
1616
import { ToZodSchema } from "core/utils/zod";
1717

1818
/**
19-
* Hashing
19+
* Hashing mapper configuration schema
20+
*
21+
* Validates hashing mapper configurations for both regular and data activation connections.
22+
*
23+
* fieldNameSuffix: Appended to the field name after hashing (e.g., "_hashed" → "email_hashed")
24+
* - Regular connections: typically use non-empty suffix like "_hashed"
25+
* - Data activation connections: use empty string "" to allow mapper chaining on same field
2026
*/
2127
export const hashingMapperConfiguration = z.object({
22-
fieldNameSuffix: z.string().nonempty("form.empty.error"),
28+
fieldNameSuffix: z.string(),
2329
method: z.nativeEnum(HashingMapperConfigurationMethod),
2430
targetField: z.string().nonempty("form.empty.error"),
2531
} satisfies ToZodSchema<HashingMapperConfiguration>);

0 commit comments

Comments
 (0)