We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In #8074 we discovered that core-amqp's validate() method will helpfully do a string-izing of the entity path field in the connection options.
Unfortunately, if the field is undefined it actually stringizes it instead, leaving you with entityPath: 'undefined'.
We should fix this and just make sure nobody is depending on it working that way in our code (EH and SB).
(NOTE: SB should be fine but you can remove the workaround I added after you fix this)
The text was updated successfully, but these errors were encountered:
undefined
[Core AMQP] Do not stringify entityPath for undefined (#12321)
1e8ad24
Fixes #8105 and #11155
HarshaNalluru
Successfully merging a pull request may close this issue.
In #8074 we discovered that core-amqp's validate() method will helpfully do a string-izing of the entity path field in the connection options.
Unfortunately, if the field is undefined it actually stringizes it instead, leaving you with entityPath: 'undefined'.
We should fix this and just make sure nobody is depending on it working that way in our code (EH and SB).
(NOTE: SB should be fine but you can remove the workaround I added after you fix this)
The text was updated successfully, but these errors were encountered: