You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The solution to fix this is to not use the same request class for 2 different API routes/methods.
One of the motivations to develop this LRD was to actually identify bad design patterns that can lead to spaghetti.
My suggestion is that you could choose to use inheritance and that would make your code much cleaner and more scalable.
Having said so, after our UI renewal #103, I ll work on addressing support to somewhat similar problem, where LRD be able to generate missing documentation by calling the actual API on top of what we already have - reflection class.
@kevincobain2000 OK thanks for the advice. I will consider separating the classes for the different methods and I can't wait for the new update from this package.
hi, I'm new here
when I try to use isMethod condition in Request Class, the documentation does't show like below.
my request
documentation
is there any solution regarding this? thx
The text was updated successfully, but these errors were encountered: