I've got a couple of minor improvements for the wsclient_tester module. The accompanying patch includes the following:

  1. Tester form should pass default variables set in client definition instead of being empty.
  2. The module should adhere to drupal code style (as much as possible).
  3. Tester form text fields should be wider so you can read longer variables.

Let me know what you think.

CommentFileSizeAuthor
wsclient-tester-improvements.patch7.31 KBbasvredeling
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dman’s picture

Status: Needs review » Reviewed & tested by the community

Yep, I'm currently going through the open issues and trying to fold in as many open patches as I can right now - *because* I then want to do a code style update after that. :-)
It's a pain trying to fix the little phpcs complaints and then re-roll all the hard stuff, so doing it in the other order.

Patch looks clean and sane.
I'm working on setting up a bit more of a testing/regression harness for wsclient right now, so will try to apply it when I've settled that dust.

basvredeling’s picture

Do you need a patch without the code style cleanup? So you can apply this patch and do your own code style fixes?

dman’s picture

Nope, don't worry about that. There is nothing pending in the tester module issues that would conflict.
A *couple* of incidental tidy-ups as we go is fine when you are touching the code in the same place. I was just saying I've been holding myself back from max-fixing everything (Now I have PHPStorm highlighting it all for me and phpcbf on a hot-key)

I'm just saying - patch looks fine, I'm just trying to set up a testing methodology locally, and will put that thing in soon. Consider it accepted, just not applied yet.