pragmarb / pragma-migration Goto Github PK

Todos

• Abstraction to deal with decorators/contracts directly
  • Class-based pattern matching (in Base#apply_to)
  • Base#add_property, Base#transform_property etc.
• Figure out how to apply migrations on collections (e.g. Base.migrate_each?)

Notes

Not sure this is doable/we want to do it.

Todos

• Pass Rack::Request object from Rails to operations (in pragma-rails)
• Hook into Pragma::Operation to implement migration_rolled?

Notes

It's not clear right now how we can retrieve the migration repository from the operation, since we don't have access to the middleware's configuration. Perhaps we can inspect the middleware chain from the Rack environment?

We should try to improve the benchmark with different types of migrations, at least 3-4, to see the impact of different transformations on performance.

Todos

• Write integration tests with a real Pragma/Rails app
• Include in pragma-rails-starter with sensible defaults (repository and configuration)

We should store migrations under the namespace of the respective resource, e.g. API::V1::Article::Migration::RemoveIdSuffixFromAuthor.

Example

module YourApp
  class Application < Rails::Application
    config.middleware.use Pragma::Migration::Middleware, 
      repository: API::V1::MigrationRepository,
      user_version_proc: (lambda do |request|
        request.get_header('X-Api-Version') || 
          fail(Pragma::Migration::InvalidVersionError, '...')
      end)
  end
end

Notes

This could be handled by the Pragma::Operation hook, which then responds accordingly.