-
Notifications
You must be signed in to change notification settings - Fork 117
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
Mesh Testframework - key functionalities not yet implemented / mismatch with your documentation #1124
Comments
The |
The use of the client is also not documented or suggested anywhere in the documentation. |
Hello Jotschi, I came to this point via the mesh documentation: You are referring to plugin examples in the doc here: You showing the client here: GraphQlExamplePluginTest.java and in this referred test example. where you use client.setAPIKey(null) which always returns null. Sure you are using null here but there nowhere stated that this is the only thing you can do because the method returns null. |
In your current documentation of plugin development - You describe there a framework that is in fact not fully implemented.
Can you please update your documentation ? I suggest to put it into state "experimental" and warn that several functionalities are not working yet.
I wanted to use your client for some basic test scenarios - like API token access or login-based access.
com.gentics.mesh.rest.MeshLocalClientImpl
@OverRide
public MeshRestClient setLogin(String username, String password) {
// TODO Auto-generated method stub
return null;
}
Gentics Mesh Version, operating system, or hardware.
Operating System
JVM
Problem
Reproducer
Expected behaviour and actual behaviour
The text was updated successfully, but these errors were encountered: