Get the feature that exactly matches a classname containing hyphens, then look for part-matches if no exact match found. #26
Conversation
|
@SusanJaneNZ Thank you for your pull request! We are currently working on this issue, and it will be released in the coming days. |
|
Thank you. Are you able to share a link to the github branch you have your
fix on?
Also - could you please release this fix on its own, and not packaged with
other fixes?
I have several issues with bdd2octane at the moment and it is extremely
confusing to have fixes, part-fixes, and new bugs all introduced in one
version release (I am currently beta testing the 1.1.8 jar provided).
One fix per release would be incredibly helpful.
Regards,
Susan.
…On Thu, May 9, 2024 at 3:21 PM bingyujin ***@***.***> wrote:
@SusanJaneNZ <https://github.com/SusanJaneNZ> Thank you for your pull
request! We are currently working on this issue, and it will be released in
the coming days.
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGL5NMAGKBMZC7BMWWNYFS3ZBLTSNAVCNFSM6AAAAABHCYMXBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRHA3DCMJZHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
hi, the fix is in #25 |
To ensure the correct feature is found, first search for an exact match of feature description and classname. Only if this is not successful does the current logic to check for part matches (excluding hyphenated suffix) apply.