Shantanu Patil
Shantanu Patil
#24 is merged to master but I am still able to reproduce issue #19 I think the argument collector should 1. number of args is one 1. check if arg...
Because if feel Free keyword arguments (`**kwargs`) are always going to be NULL in `KeywordOverload.class` for remote server because Java itself has no kwargs syntax, but keywords can have java.util.Map...
> @shan-96 could you please create test case showing the error? Kwargs are supported, but parsed before callung to keyword for named arguments. And there're tests also for cases that...
@Hi-Fi my bad, while debugging I was using .class files from release version `2.0.3` I have anyway written a test and pushed to `develop`. I'll open a PR for the...
> So this is working, and change was only to include passing test? > > This issue is still open because of documentation updates that are in wiki are missing....
My E2E cases are still failing in production even when I deploy snapshot version of robotframework-javalibCore. I am still figuring out what is different
@Hi-Fi I have corrected the junit caught an error please check
I feel the problem is with `KeywordInvoker.java` Can you explain what does the method `KeywordInvoker.getParameterNamesFromMethod()` do?
Understood. But with this new way of parsing keyword and other args should or should not cases recorded in old library fail? When annotation is not present and names are...
Understood. But you agree that these cases should pass right? Jrobotremoteserver is latest (4.0.0)