Feedback please: 573112a. 😁

I'm testing this right now. I have already commented an issue in the README file.

@axelitus Good catch! Fixed in commit: 33db743

I found an issue with the commit 573112a, the encrypted fields are being correctly generated but an unencrypted value is being stored in the database.

I've debugged the code and the issue is related to this change introduced 21 days ago (which in fact breaks support for Laravel 5.6 also).

Previously, on insert the $this->attributes property was used directly, now $this->getAtttributes() method is called, which in fact is replaced by the HasEncryptedAttributes trait and this line gets executed which unencrypts all attribute values before insert.

The result is that the package "is broken" because it doesn't achieve it's purpose.

My proposal is to change the getAttributes() method to getUnencryptedAttributes() and use Laravel's Illuminate\Database\Eloquent\Concerns\HasAttributes::getAttributes() implementation directly, but I'm not sure if the getAttributes() is used elsewhere in your code that needs to be changed.

@axelitus Can you make a separate issue for this and include code to reproduce the bug? Without digging in too much, this seems accurate and would explain other oddities when using 5.6/5.7.

I'll open an issue later on with a use case

Closing in lieu of #30.