-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
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
Class 'Laminas\ApiTools\Admin\Controller\InputFilter\RpcService\PostInputFilter' not found #71
Comments
Do you get any error messages? If so, can you please share them? I did a manual verification of the aliases we have, and none appear to have changed; the only change was how we are resolving the legacy (ZF) aliases to the shipped classes (we are importing ZF class names in most cases). Error messages will help me better isolate the issue. Thanks! |
I created a new laminas-api-tools from scratch and this is the result I attach to you my composer.lock if you need it |
I have the identical issue. |
@weierophinney use Laminas\InputFilter\InputFilterAbstractServiceFactory;
use Laminas\ServiceManager\Factory\InvokableFactory;
use ZF\ContentValidation\InputFilter\InputFilterPlugin; |
Can I just add to this and say I am seeing a similar issue which results in the following php log: Steps to reproduce: |
is there any solution to fix this problem? |
@fmangat Thanks in advance! 👍 |
@froschdesign am not sure .looks like ModuleInputFilter is not accessible its coming under undeined classes in psalm-baseline.xml |
@froschdesign But the namespace is okay its the legacy ZF namespace or Im wrong? https://github.com/zfcampus/zf-content-validation/blob/master/src/InputFilter/InputFilterPlugin.php |
yep as per rewrites rulesits correcr...... it s very odd that the basic installation is not working |
its not something related to configs? |
You are right and the
Please try to delete the cache for the config. |
@froschdesign I dont know why but when we update to 1.10.0 the listener cant find the filter, look at my image the line: 1768 its what I added, the full namespace and works but above is the package declaration and at the left of the file is the path to the file thats its okay, so strange |
@diego-sorribas
Please only one problem at a time, otherwise we will not reach any goal. Thanks! |
@froschdesign It seems to be all related to the module.config.php. |
@diego-sorribas Can you check the classnames and namespaces? The classes are there and under namespace https://github.com/laminas-api-tools/api-tools-admin/tree/1.11.x/src/InputFilter/RestService |
"laminas-api-tools/api-tools-admin": "1.9.0", i have downgraded api-tools-admin version to 1.9.0 which worked for now |
This is a namespace issue in the module.config.php file. The namespace Just replace the input filter configuration with the following snipped. This one worked fine for me.
This can not be the solution of this problem. We all should look why the |
This issue still stands unresolved. I've downgraded to 1.9.0 and it works fine. Why does it work for few and not for others or everyone has downgraded to 1.9.0 to make it work? How long is it going to take to fix it? any idea? |
- Input filters, in particular, were mapped such that the POST/PATCH input filters were invalid - Legacy Apigility classes were mapped in such a way that Laminas service names might never match. The solution for this is to always list Apigility classes in quotations, and ensure that any `::class` notation is reserved for real classes and/or Laminas pseudo-classes. Fixes laminas-api-tools#71 Signed-off-by: Matthew Weier O'Phinney <[email protected]>
Fixed with #79 |
BC Break Report
Summary
After upgrading to 1.10.0 from 1.9.0 I want to create a RPC service from the UI and launch me that error. I think there is some error in the aliases config. When I inspect with PhpStorm the new vendor/laminas-api-tools/api-tools-admin/config/module.config.php it cant resolve the PostInputFilter location.
Previous behavior
Create RPC services without error.
Current behavior
Can't create RPC services from api tools admin ui.
How to reproduce
The text was updated successfully, but these errors were encountered: