Mature AEM Utils Helper Class
The current AEM utils are a loosely structured set of helper methods within a utility class. As we continue to expand support for both AEM HTTP APIs and AEM Open APIs—which have significantly different authentication and interaction patterns—it would be beneficial to formalize this into a TypeScript-based class structure.
Proposal:
• Create a strongly typed AemApiHelper class that encapsulates both HTTP and Open API interactions.
• Introduce a unified initialization method that accepts a multi-auth config (e.g., S2S, JWT, or user-based auth).
• Each API call should validate that the appropriate authentication method has been initialized, and throw a clear error if not.
• For calls that support multiple auth types, allow the caller to optionally specify which one to use.
Mature AEM Utils Helper Class
The current AEM utils are a loosely structured set of helper methods within a utility class. As we continue to expand support for both AEM HTTP APIs and AEM Open APIs—which have significantly different authentication and interaction patterns—it would be beneficial to formalize this into a TypeScript-based class structure.
Proposal:
• Create a strongly typed AemApiHelper class that encapsulates both HTTP and Open API interactions.
• Introduce a unified initialization method that accepts a multi-auth config (e.g., S2S, JWT, or user-based auth).
• Each API call should validate that the appropriate authentication method has been initialized, and throw a clear error if not.
• For calls that support multiple auth types, allow the caller to optionally specify which one to use.