Since the pull requestcycle/database#226 has been merged, it might be a good idea to ignore thefirst andafter attributes when equaling the default values? So migrations are not declaring them for every column when not needed.

🔍 What was changed

• Added logic to ignore thefirst andafter attributes when equaling the default values.
• Added some test cases (using Reflection) for theRenderer::columnOptions method.

🤔 Why?

When thinking about how column positioning would be used in migrations, I'm of the opinion they would be defined manually. As in I can't imagine defining this for an entity, instead I'd likely generate a migration, say containing an added column and then modify the options to position the new column after and existing column, to suit an order I prefer.

publicfunctionup():void    {$this->table('api_key')->addColumn('expires_at','datetime', ['nullable' =>true,'defaultValue' =>null,'comment' =>'Date and time API key will expire','after' =>'updated_at',        ]);    }

📝 Checklist

• How was this tested:
  • Unit tests added