Issue1346 deal with change in semantics for queue declares from previous versions.

[petersilva]

there is a change in required order in configuration files that needs to happen because in future, there will be support for connections to multiple queues and multiple brokers from the same subscriber.

For current versions, this means parameters applied to queues need to be earlier in the file than when queue settings get resolved. This happens when the parser reaches as subtopic setting. So in this set of patches:

• in sr3 convert... move the affected options to the front of the file ... since v2 only supported single queues, this is good.
• in config parser, make a warning message for when settings show up in a fishy place... after subtopic.
• add some hints in the reference about ordering constraints.

[github-actions]

Test Results

5 tests   0 ✅  18s ⏱️
1 suites  0 💤
1 files    0 ❌  5 🔥

For more details on these errors, see this check.

Results for commit 6f7337e.