Amy's Array of Errors

[arrayoferrors]

Goodnight!

Another live blog is finished, as Billmation 2.0 continues to move closer to being finished.

Please join me again for another live blog this Saturday, which will be a special extended edition! 

[arrayoferrors]

And recurring charges is complete!

The last piece of the puzzle was adding the ability to link taxes with a recurring charge. Now that this is done, the CRUD for recurring charges is finished. The next step will be adding scheduled invoices.

[arrayoferrors]

And now we can save recurring charges.

I've created the method to save recurring charges, so now Billmation can both add new recurring charges and edit existing ones. In addition, this method uses the Billmation validation system which is built off of Zend\Validate. It is similar to how Zend\Form uses InputFilter, although doesn't use the same code. This is in part because I was not as familiar with Zend\Form and InputFilters when I started this, and in part because we aren't using the Zend\Form functionality in our SOA. Still, we're using the same validators used when using Zend\Form.

[arrayoferrors]

A common misconception by all the cool cats on the Internet is that Billmation is not yet live and operational. Yes, it's true Billmation 2.0 is not ready, working its way ever so slowly to completion. However, the original version of Billmation is most definitely running. If you have a need for creating invoices quickly and easily, or just want to see what this live blog's fuss is all about, go check it out. The account is free, and we'd appreciate the feedback.

[arrayoferrors]

What I'm watching tonight

First I'll be finishing off an episode of Saturday Night Live, which is taking forever to finish due to intermittent internet. After that, I'll be switching to my replacement copy of Pirates of Silicon Valley. Hopefully this one will work better than my old copy.

[arrayoferrors]

Let the Live Blog Begin!

Another Tuesday night, another coding live blog. I start where I left off, which means I will continue with the automation system. Looks like we still have some crud to accomplish for recurring charges, so let's get to it!

[arrayoferrors]

And we Have Another Action Method

Alright, I've added another action method for recurring charges, this time deleteRecurringCharges. With that, the basic delete and list functionality for recurring charges is now part of Billmation 2.0.

Now that this is done, this completes the portion of the coding marathon that I will be live blogging. Check back here next Tuesday, as I continue the slow progress of getting this finished.

[arrayoferrors]

Oops...

When adding the ability to delete recurringCharges, I discovered that my code did filter by the current Billmation account, so it was returning all of the recurringCharges in the entire database. Suffice it to say this would be bad had it reached production.

Fortunately, I caught this early, and it is showing only the recurring charges for the given account.

[arrayoferrors]

Well, that was easy

Adding the customer filter to getRecurringCharges turned out to be a quick task. It helped that the code was already set up, it just needed the parameter passed into the service.

At this point, I believe I will move on to finishing the rest of the CRUD calls for recurring charges. Once that is done, it will be on to scheduled invoices.

[arrayoferrors]

What I'm Watching during the Marathon

No movie, at least not right now. Instead I've got SNL on Netlfix. I'm trying to go through the episodes in the short time they will still be there. It actually works fairly well as the background to coding. I'm currently on the 2002-03 season, which is about a year or two after I stopped regularly watching the show in its initial run.

[arrayoferrors]

Last time on Tuesday Night Coding...

During the last coding marathon, I created the action method that is used to get recurring charges. As of right now this returns all recurring charges, Before I continue, I need to add a way to filter by customer. 

Hmm....that sounds like a good first step. I think I'll proceed that way.

[arrayoferrors]

Let's Get Started

Coding Marathon #3 has begun! It was delayed a bit because of a construction issue (not related to code) that kind of had to be taken care of before I could begin.

Tonight I will continue work on Automation in Billmation. However, i will also be spending time on another project I am doing for my day job, which is facing a hard deadline. I'm afraid I can't give any details about it. It's possible my posts may be infrequent during that session.

Alright, let's get coding!

[arrayoferrors]

Tuesday Night Coding will begin...in about 30 minutes

Unlike last week, we're on for this week. However, it probably won't be for another 30 minutes or so. Until then, just chill out, because I know you all are giddy with anticipation for another night of Tuesday Night Coding.

[arrayoferrors]

Tuesday Night Coding Postponed until Thursday Night

Due to the holiday weekend (and thus due to getting back from my parents at 2:30 this morning), the coding marathon will be postponed until Thursday night. Hopefully that night I'll have had a better night's sleep to work with.

[arrayoferrors]

And...Goodnight!

OK, Another coding marathon is in the books. This time was much more productive, as I was able to get some methods testing, and one of the action methods working for the Automation controller. Here's hoping next week will be even more productive.

Until next week, everybody!

[arrayoferrors]

This mess is the result of the methods that I tested and wrote tonight. The part above the line is the JSON encoded response that is echoed out for use by the front-end code. The part below the line is just the result decoded and output in a readable format using print_r().

Just like that, this is ready to use and be tested with. Either another method in the controller, or parameters for this action method will allow the list to be filtered by customer. But that is for another night.

[arrayoferrors]

Here’s the code coverage report after one night of work. Yeah, it’s pretty terrible, but I’ve only created tests for two classes so far. Of all of the great things about using PHPUnit, having the code coverage report in an easy to read HTML form is my favorite.