[hoanle0126]

Summary

has_create_action?/1 in AshPostgres.MigrationGenerator previously excluded create actions that set manual. Because extensions like AshEvents wrap resource create actions as manual actions, resources using AshEvents reported has_create_action: false, causing count_with_create to be 0 when multiple evented resources share a table and marking subtype-specific allow_nil?: false columns as null: false in generated migrations.

Since manual create actions still insert rows into the underlying table, this updates has_create_action?/1 to count all :create actions regardless of whether manual is set.

Closes #851

Contributor Checklist

• I have read and understood the Contributing Guidelines
• I have added tests for the changes

[zachdaniel]

I don't think this is right. It's not a given that a manual create action interacts with the data layer. See my comment on that issue:

Yeah this is a bit of a head-scratcher architecturally. We want that check in general but we may need to add a special option just for this case like always_create_migrations? true 😓. It's not ideal. Can you talk with @Torkan in an AshEvents issue and see what he thinks?