Fix to make Symfony Finder component optional#267
Fix to make Symfony Finder component optional#267bigdevlarry wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
68bd923 to
bc19684
Compare
eb1a5f9 to
abf1b30
Compare
dd9bfef to
6e8e705
Compare
|
Can you also add a change to https://github.com/modelcontextprotocol/php-sdk/blob/main/src/Server/Builder.php#L526 ? Avoid calling the |
|
@soyuka, this means the discoverer will never be called if there's no finder, and we won't be able to raise the exception to prompt the installation of the finder itself. By your suggestion, adding a null check silences the error in the logs, and the program continues as expected. Is this the ideal behaviour, or should we halt the program with the exception as we have it, so users go back to install? Let me know what you think as well @chr-hertel |
|
Mhh from this PR I thought you wanted to move the If we don't want to move this requirement, then I'm not sure I understand how this code path is going to happen as its required in our dependencies. |
Motivation and Context
The changes make the Symfony Finder component optional, as referenced in issue #263
How Has This Been Tested?
Yes
Breaking Changes
Not a breaking change
Types of changes
Checklist
Additional context