Describe the feature

Currently the size of ingested document chunks is hardcoded in the embeddings Lambda function (Fixed-size chunking).
However, depending on the scenario and content ingested, the user might need to apply a different strategy.

Use Case

More flexibility for the end user

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Update the code for use without deprecation

Use Case

Prepare for next major release. Building the library causes warnings like:

[WARNING] aws-cdk-lib.aws_appsync.GraphqlApiProps#schema is deprecated.
use Definition.schema instead
This API will be removed in the next major release.

Proposed Solution

use Definition.schema instead

Other Information

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_appsync.GraphqlApiProps.html
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_appsync.Definition.html

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

OpenSearch Serverless support : currently the constructs support only a provisioned OpenSearch cluster

Use Case

Reduction in complexity, autoscaling

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the issue

Update cost estimates in documentation + default properties following recent add ons (VPC flow logs,...)

Links

https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/src every README

Describe the feature

Hello,

Here is Philipp from Hugging Face. I am leading the partnership between AWS and Hugging Face from a technical side.
I just came across this fantastic library and project. Is there something we can do to make it easier for you to improve and maintain the library, e.g. notify about new feature, versions etc.

Use Case

.

Proposed Solution

.

Other Information

.

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Provide a user management strategy to store user related information and enable additional features in constructs (feedback on generated responses, ...)

Use Case

Provide additional features in constructs

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Add a construct to enable deployment of custom models to a SageMaker endpoint (fine tuned, inf2,...)
This construct should provide the user the ability to point towards a location in Amazon S3 where the model artifacts are located, and a DLC container image

Use Case

More flexibility and customization for end users

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

This construct deploys Langserv a FastAPI based framework that helps developers deploy LangChain's Runnables and Chains as REST API in production.

Use Case

Langserv simplifies the deployment of Large language Models from a prototype to production with industry best practices such as

1. API docs page with JSONSchema and Swagger
2. Efficient /invoke/, /batch/ and /stream/ endpoints with support for many concurrent requests on a single server
3. All built with battle-tested open-source Python libraries like FastAPI, Pydantic, uvloop and asyncio
4. FastAPI is a modern, fast (high-performance), web framework for building APIs with Python 3.8+ based on standard Python type hints.
5. Observability and Analytics
6. LLM Provider Agnostic

Proposed Solution

At a high level this construct will deploy LangServ and LangFuse on AWS using Services such as Fargate, ECS and RDS but will depend on existing constructs such as aws_ecs_patterns. Developers will be able to make custom REST api calls to FastAPI endpoints with support for streaming, batch and invoke. The construct will be LLM provider agnostic such as Bedrock, SageMaker or VLLM on EC2 Instances giving developers flexibility to experiment with different model providers.
The construct will also provide monitoring and observability capability using LangFuse giving developers the flexibility to trace and debug LLM applications, monitor latency and model evaluation capabilities.

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the bug

Some resources in #169 require physical names of 32 characters or less. The resulting string for a given prefix will always be the same and longer than 36 characters.

AWS::OpenSearchServerless::Collection
AWS::OpenSearchServerless::AccessPolicy
AWS::OpenSearchServerless::SecurityPolicy

Expected Behavior

For maxLength < 36, generatePhysicalName will return a unique string of size maxLength.

Current Behavior

Since the stackIdGuidLength is 36, the parts will be truncated to 0, and the resulting string will be the prefix plus the GUID. The resulting string for a given prefix will always be the same and longer than 36 characters.

Reproduction Steps

n/a

Possible Solution

Completely changing the algorithm will break existing stacks, so if maxLength is less than prefixLength + stackIdGuidLength, use an alternative algorithm.

Create a truncated hash of 8? characters. Use the existing algorithm to combine prefix, parts, and the short hash.

Additional Information/Context

No response

CDK CLI Version

n/a

Framework Version

No response

Node.js Version

n/a

OS

n/a

Language

Typescript

Language Version

No response

Region experiencing the issue

all

Code modification

n/a

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

Describe the feature

Evaluate Terraform support for constructs

Use Case

More flexibility for end user

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Profile and optimize performances for the https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/src/patterns/gen-ai/aws-qa-appsync-opensearch construct

Use Case

better user experience

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Update libraries in the requirements.txt file

Use Case

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

• Add missing features to the Lambda layer construct
• Refactor Q/A, Data ingestion and Summarization constructs to use the updated Lambda layer

Use Case

Facilitate sustaining
Enable more customization and flexibility in existing constructs (select models outside of Amazon Bedrock, ...)

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Issue Metrics

This report was generated with the Issue Metrics Action
Search query used to find these items: repo:awslabs/generative-ai-cdk-constructs is:issue created:2024-01-01..2024-01-31 -reason:"not planned"

Describe the feature

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_sagemaker.CfnModel.html#vpcconfig CfnModel allows users to pass the VpcConfig, we should provide that possibility to users as well

Use Case

Control access to and from your model container by configuring the VPC.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Allow for adding a KnowledgeBase to an agent and not only to specify existing KBs at the agent construct instantiation.

Use Case

Allow for more flexibility in the order in which agents and KBs are created

Proposed Solution

Implement a Agent.addKnowldgeBase(KnowledgeBase, {instructions}) and a KnowledgeBase.assToAgent(Agent, {instruxtions}) methods

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

I'd like to be able to use AWS Inferentia for my endpoint inference containers

Use Case

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the issue

The README for the aws-rag-appsync-stepfn-opensearch pattern includes the following import:

import { RagApiGatewayOpensearch, RagApiGatewayOpensearchProps } from '@cdklabs/generative-ai-cdk-constructs';

However, you can see in lines 124-127 of the aws-rag-appsync-stepfn-opensearch/index.d.ts file that you've changed the name of the export. The comment references the old name and the export references thange from ApiGateway to AppSync.

/**
   * @summary The RagApiGatewayOpensearch class.
   */
export class RagAppsyncStepfnOpensearch extends Construct {

Please update the pattern README to reflect a working deployment.

Also, some customers may prefer API Gateway to AppSync due to familiarity, so maybe making both an option going forward would be best.

Links

https://github.com/awslabs/generative-ai-cdk-constructs/blob/main/src/patterns/gen-ai/aws-rag-appsync-stepfn-opensearch/README.md

Describe the feature

Currently, the https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/src/patterns/gen-ai/aws-qa-appsync-opensearch construct's logic uses a long context window approach if a document name is specified. However, the end user might want to choose a RAG approach.

Use Case

Provide more flexibility to the end user

Proposed Solution

Add a new parameter to the GraphQL schema to select the method

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Issue Metrics

This report was generated with the Issue Metrics Action
Search query used to find these items: repo:aws-samples/emerging-tech-cdk-constructs is:pr created:2023-09-01..2023-09-30 -is:draft

Describe the feature

When an Agent, Knowledge Base, or Action Group is created or updated, the agent needs to be prepared by calling the PrepareAgent API. There is already a custom resource to call PrepareAgent, but it is only available within the Agent resource. It is preferable to only call PrepareAgent once after all updates are made.

I would like to be able to add dependencies and optionally a changeId to the PrepareAgent custom resource from outside of the Agent resource.

Use Case

While developing Agent Action Groups, I see that there needs to be a public way to add a dependency to Prepare Agent. Agent Action Groups depend on an Agent, but the Agent needs to be prepared after creating or updating the Agent Action Group.

Proposed Solution

An internal method on Agent called _addPrepareAgentDependency can be called to add a resource and optionally a changeId so CloudFormation knows to update PrepareAgent when the resource is updated.

/**
 * Register a dependency for prepareAgent.
 *
 * @param resource - The resource that will be registered as a dependency.
 * @param changeId - The changeId of the resource that will be registered as a dependency.
 *
 * @internal This is an internal core function and should not be called directly.
 */
public _addPrepareAgentDependency(resource: cdk.IResource, changeId?: string) {
  this.prepareAgent.node.addDependency(resource);
  if (changeId) {
    this.changeIds.push(changeId);
  }
}

Usage:

props.agent._addPrepareAgentDependency(agentActionGroup, agentActionGroup.getAttString('changeId'));

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the issue

Update diagrams project with latest architecture diagram updates
The project seems out of sync as diagrams for each construct have newer icons

Links

https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/docs

Describe the feature

Current data ingestion pipeline supports PDF files only, we should support additional text file formats (csv,...)

Use Case

Extend the capabilities of the construct

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Evaluate a semantic caching strategy for Q/A, and which could be reused for other constructs as well

Use Case

Reduce cost and improve user experience

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Upload a video or audio file to the construct and then generate a summary of the input file or perform question answer on it.

Use Case

There is a lot on content available in the form of audio and video content , for example podcast recordings , customer care telephonic call , real time govt/corporate policy call out videos. A quick highlighted summary or handling specific question answer on these content will help customer in making their business decisions.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Issue Metrics

This report was generated with the Issue Metrics Action
Search query used to find these items: repo:awslabs/generative-ai-cdk-constructs is:pr created:2024-01-01..2024-01-31 -is:draft

Describe the feature

Enable vpc endpoint to access S3 and other resources from lambda in private subnet.

Use Case

As of now, the lambda use NAT gateway to access any public endpoint which should be avoided as per security best practices. The VPC endpoint enable the construct to skip any routing on the public network.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the issue

Each construct README provides a code snippet for Typescript (minimum deployable pattern definition), however there is no code snippet for Python

Links

https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/src/patterns/gen-ai -> every README

Issue Metrics

no issues found for the given search criteria

This report was generated with the Issue Metrics Action

Describe the feature

Data ingestion, Q/A and Summarization currently use Appsync, however supporting API gateway
Need to evaluate if this could be a variation of existing constructs or new ones

Use Case

More flexibility for end user

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the bug

I'm using the QaAppsyncOpensearch construct (https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/src/patterns/gen-ai/aws-qa-appsync-opensearch) with a new created OpenSearch. The Lambda logs keep complaining about not can find the index. But as of my understanding the index should be created automatically when it can't be found.

[ERROR] NotFoundError: NotFoundError(404, 'index_not_found_exception', 'no such index', demoindex, index_or_alias)
Traceback (most recent call last):

I'm adding OpenSearch like that:

      const osDomain = new os.Domain(stack, "Domain", {
        version: os.EngineVersion.ELASTICSEARCH_2_3,
        capacity: {
          masterNodeInstanceType: "t2.micro.search",
          dataNodeInstanceType: "t2.micro.search",
        },
        removalPolicy: cdk.RemovalPolicy.DESTROY,
      });

Expected Behavior

AppSync request is successful

Current Behavior

AppSync keeps on status "Working on the question"

Reproduction Steps

Create a simple CDK deployment like that and run the AppSync subscription and mutation

      const osDomain = new os.Domain(stack, "Domain", {
        version: os.EngineVersion.ELASTICSEARCH_2_3,
        capacity: {
          masterNodeInstanceType: "t2.micro.search",
          dataNodeInstanceType: "t2.micro.search",
        },
        removalPolicy: cdk.RemovalPolicy.DESTROY,
      });

      const rag_source = new QaAppsyncOpensearch(this, "QaAppsyncOpensearch", {
        existingOpensearchDomain: osDomain,
        openSearchIndexName: 'demoindex',
        cognitoUserPool: cognito.cdk.userPool,
      });
      rag_source.s3InputAssetsBucket?.applyRemovalPolicy(
        cdk.RemovalPolicy.DESTROY
      );

Possible Solution

Maybe my OpenSearch is to low tier?

Additional Information/Context

No response

CDK CLI Version

2.124.0

Framework Version

No response

Node.js Version

20

OS

mac

Language

Typescript

Language Version

No response

Region experiencing the issue

us-east-1

Code modification

..

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

Describe the feature

Every instance of a classic AWS service should be created through a common helper function to ensure consistency and use of best practices across constructs

Use Case

simplify sustaining and development of new constructs

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

no issues found for the given search criteria

Describe the feature

Many RAG experiences are built around websites. Users want to crawl one or more websites, retrieve content from pages, schedule periodic updates, and inject results into OpenSearch to enable RAG requests based on website data.

To support this scenario, a WebCrawler construct can be created. It should be capable of creating new OpenSearch indexes or using existing ones.

This construct can also be used to obtain data from websites in real-time. For example, a user could ask a chatbot to summarize a specific webpage. In this case, the web crawler should extract data from the webpage and provide it to the chatbot.

We should also consider web search scenarios, where users want to use a search engine to obtain results. The results found by the search engine should be parsed and returned to the chatbot.

Use Case

RAG over websites

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

The 5.1 release line of jsii will reach End-of-Support soon, on 2024-02-28T00:00:00.000Z.          !!
!!  We strongly recommend you upgrade to the current release line (5.3) at your earliest convenience.  !!
!!                                                                                                     !!
!!  Other actively supported release lines include:                                                    !!
!!  - 5.2 (planned End-of-Support date: 2024-06-30T00:00:00.000Z) 

Use Case

upgrade dependency

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Provide a new construct which can provide responsible AI features for existing constructs, such as monitoring and analytics

Use Case

Additional features for existing constructs

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Adding the possibility to ask user for complementing information to complete a task is implemented by adding a special Action Group to an agent.
This can be done currently with the CDK construct, but require the developer to know the details on how this action groups should be configured. It would be more developer friendly to just have a boolean value enableUserInput in the Agent creation props, which gets translated into the necessary group configuration.

Use Case

Enable Agents to ask for user input

Proposed Solution

Implement a enableUserInput boolean property in the Agent props.
If true automatically create and add the ActionGroup configured as:

{
  'actionGroupName': 'UserInputAction',
  'parentActionSignature': 'AMAZON.UserInput',
  'actionGroupState': 'ENABLED'
}

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the issue

Update documentation to include the following changes:

• PR template with link to contributing guidelines, checkbox for unit tests
• Update developer documentation to explain the tools recently put in place (husky, commintlint,...)
• Update contributing guidelines, tenets

Links

contributing, development guidelines, PR template

Describe the bug

So I noticed that newlines are getting removed when RAG is transforming from pdf to txt. That probably decreases the level of accuracy when using similarity search.

I kind of hat a workaround as my ingestion files don't need bo PDFs so I just could take the txt file like and leave it as it is for the embedding:

---
event: meetup
title: Langchain AI MVP
date: "2024-02-03"
tags: ["meetup", "langchain"]
---

0:00:00.719,0:00:03.719
okay

0:00:05.400,0:00:09.120
awesome so I will start with the first

0:00:07.980,0:00:11.460
talk

0:00:09.120,0:00:14.280
uh thanks again for attending here to

I'm sure that had better results then without newlines!

Expected Behavior

Newlines are not removed

Current Behavior

Newlines are removed

Reproduction Steps

do a RAG and view the txt file.

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.124.0

Framework Version

No response

Node.js Version

20

OS

macos

Language

Typescript

Language Version

No response

Region experiencing the issue

us-east-1

Code modification

....

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

Describe the feature

Currently, the generation of the list of available models/containers needs to be manually triggered
We need to add a projen task which generates the list of models/containers, then a Github action which can run on a schedule and open a PR (every 48 hours) if there is anything new

Use Case

Automation, facilitate sustaining

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Constructs and easy to run on GovCloud not the public cloud

Use Case

GovCloud customers have different restrictions

Proposed Solution

Separate Repo or section?

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Amazon Bedrock recently unveiled some features which are not available through CDK at the moment (Guardrails, knowledge bases, agents).

Use Case

Provide new features for end users

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Allow a prop like readonly lambdaProvisionedConcurrency?: number; for the QA construct.

Use Case

I would like to configure provisioned concurrency for the lambda function provisioned by the QA construct to minimize cold-starts to squeeze out a bit more performance on client applications.

Proposed Solution

In src/patterns/gen-ai/aws-qa-appsync-opensearch/index.ts add an optional prop and then in the lambda resource, conditionally add the provisioned concurrency in the configuration.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the bug

Agent.addAlias requires an agentId prop, but the instance of the Agent already has an agentId field.

Expected Behavior

I can call agent.addAlias({aliasName: 'prod'})

Current Behavior

I must include agentId in the props: agent.addAlias({agentId: agent.agentId, aliasName: 'prod'}).

Reproduction Steps

n/a

Possible Solution

Since JSII doesn't support the Omit or Partial types, the method needs its own interface. It can either be a copy of AgentAliasProps with the unwanted types removed, or https://github.com/mrgrain/jsii-struct-builder could be used.

Additional Information/Context

The changeIds prop can be removed too with #229 .

CDK CLI Version

n/a

Framework Version

No response

Node.js Version

n/a

OS

n/a

Language

Typescript

Language Version

No response

Region experiencing the issue

n/a

Code modification

no

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

Describe the feature

Allow to import existing collections and indexes to be used in the stack

Use Case

Customers might have already collections they want to use as a Bedrock Knowledge Base

Proposed Solution

Allow importing existing resources

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Current implementation uses Anthropic Claude v2.0, request to update to Anthropic Claude v2.1

Use Case

https://www.anthropic.com/index/claude-2-1
Longer context windows, reduced hallucinations

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the feature

Build a construct for image generation using Amazon Bedrock's Stable Diffusion XL
Backend only, a sample solution with a UI can then be built

Use Case

Expanding catalog

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Describe the bug

I'm unable to deploy the SageMaker endpoint using the JumpStartSageMakerEndpoint construct.

Expected Behavior

The endpoint gets created.

Current Behavior

CloudFormation throws the following error when trying to create the endpoint:

Could not find model data at s3://jumpstart-cache-prod-us-east-1/huggingface-asr/huggingface-asr-whisper-base/artifacts/inference-prepack/v1.0.1/. (Service: AmazonSageMaker; Status Code: 400; Error Code: ValidationException; Request ID: 8e830934-e61a-4c1e-96e5-1663211204b0; Proxy: null)

Reproduction Steps

import * as cdk from "aws-cdk-lib";
import { Construct } from "constructs";
import {
  JumpStartModel,
  SageMakerInstanceType,
  JumpStartSageMakerEndpoint,
} from "@cdklabs/generative-ai-cdk-constructs";

export class SagemakerJumpStartFmEndpointStack extends cdk.Stack {
  jumpStartEndpoint: JumpStartSageMakerEndpoint;

  constructor(scope: Construct, id: string, props: SagemakerJumpStartFmEndpointStackProps) {
    super(scope, id, props);

    this.jumpStartEndpoint = new JumpStartSageMakerEndpoint(this, "JumpStartEndpoint", {
      model: JumpStartModel.HUGGINGFACE_ASR_WHISPER_BASE_2_0_0,
      instanceType: SageMakerInstanceType.of("ml.g5.2xlarge"),
    });
}

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.111.0

Framework Version

0.1.11

Node.js Version

21.4.0

OS

Mac OS

Language

Typescript

Language Version

No response

Region experiencing the issue

us-east-1

Code modification

No

Other information

No response

Service quota

• I have reviewed the service quotas for this construct

Issue Metrics

This report was generated with the Issue Metrics Action
Search query used to find these items: repo:awslabs/generative-ai-cdk-constructs is:pr created:2023-11-01..2023-11-30 -is:draft

Describe the feature

I'd like to be able to use stores other than Amazon OpenSearch Serverless.

Use Case

Amazon OpenSearch Serverless is riding on serverless fame or low costs, yet it's one of the most ridiculously priced services.

The minimal cost of running an Amazon OpenSearch Serverless index is ~ $700/mo.

Source:

• https://repost.aws/questions/QUAc9Mg6avRCy3e5kOF8v5fQ/pricing-strategy-for-open-search-serverless
• https://repost.aws/questions/QUPxlXCMbVSdqLvCqQcW-lMw/clarification-on-opensearch-serverless-pricing

Proposed Solution

Provide options for other storage backends that are more reasonably priced.

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change