Issue #156 resolved
Alembic doesn't throw TypeError on unexpected keyword arguments
Alembic shouldn't just ignore keyword arguments that are not used. I recently typod "postgesql_where" and to my surprise, Alembic just went along with it and created an invalid index.
op.create_index( "uq_index_user_email_reseller_is_null", "user", ['email'], postresql_where=text("reseller_id IS NULL"), unique=True )
What I expected:
TypeError: op.create_index() got an unexpected keyword argument 'postresql_where'