Configurable message source name delimiter in tests
See original GitHub issueI’m in the process of creating a binder implementation for Amazon SQS which unfortunately doesn’t allow the period (.) character in queue names. From http://docs.aws.amazon.com/cli/latest/reference/sqs/create-queue.html:
The name of the new queue. The following limits apply to this name:
- A queue name can have up to 80 characters.
- Valid values: alphanumeric characters, hyphens (- ), and underscores (_ ).
- A FIFO queue name must end with the .fifo suffix.
Queue names are case-sensitive.
The abstract test classes use hardcoded names such as foo.0 which result in 400 errors from the SQS API. I’d like to provide a hook to be able to override the message source/target name delimiter so such a name could be foo-0 instead. I’d be happy to submit a PR but want to make sure this would be a welcomed change.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Format of delimited messages - IBM
Delimited messages represent changed records as fields that are separated by a character, such as a comma.
Read more >Delimited text format in Azure Data Factory - Microsoft Learn
This topic describes how to deal with delimited text format in Azure Data Factory and Azure Synapse Analytics.
Read more >Guide to JUnit 5 Parameterized Tests - Baeldung
Learn how to simplify test coverage in JUnit 5 with parameterized tests. ... the delimiter is customizable with the delimiter attribute.
Read more >Delimited File Sources — Virtual DataPort Administration Guide
This type of source retrieves data from text files in CSV (Comma Separated Values) format or similar. Complex regular expressions can also be...
Read more >Configuring Delimited File Properties
When you read data from a delimited file, you can edit file properties in the session, such as the delimiter or code page....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks; I was just trying to point out that the origin of the names in the tests was from XD (SCDF’s predecessor), so just “fixing” the tests isn’t a total solution.
@JacobASeverson I wonder if a simpler approach would be to change the queue names in Abstract test classes to something commonly accepted (i.e., underscores
foo_0) In any event your contribution is definitely welcomed and we can debate some of the details later when you have a PR.