This should be replaced with middleware and/or policies

Class App

Move LDAP methods into user model for better separation of concerns.

Refactor this nastiness. Assets do not behave the same as accessories, etc.

Member App::getDataView ($categoryID)

Refactor this nastiness. Assets do not behave the same as accessories, etc. Need to figure out if I should make separate controllers, or what. Too much copypasta if I try to work it in here.

Class App

Improve documentation here.

Check for raw DB queries and try to convert them to query builder statements

Member App::edit ($id)

Uhh, build this?

Member App::update ($id)

Uhh, build this too?

Member App::getFreeLicense ($licenseId)

This is a dumb way to solve this problem. Author should refactor. And go hide in a hole and think about what she's done. And perhaps find a new line of work. And get in the sea.

Member App::postCheckout ($seatId)

Switch to using a FormRequest for validation here.

Member App::postUpload ($licenseId=null)

Switch to using the AssetFileRequest form request validator.

Member App::getDataViewAssets ($locationID)

This is broken for accessories and consumables.

Member App::postCreate ()

Check if a Form Request would work better here.

Member App::store ()

Check if a Form Request would work better here.

Class App

Move this to a more Laravel 5.2 esque way

Member App::remove (Builder $builder)

IMPLEMENT Remove the scope from the given Eloquent query builder.

Class App

Move this to a more Laravel 5.2 esque way

Member App::remove (Builder $builder)

IMPLEMENT Remove the scope from the given Eloquent query builder.