Feature/534

[josephmancuso]

This PR introduces the concept of Provider Publishing. This is the concept of a provider being responsible for adding files to an application like migrations or routes or templates.

[josephmancuso]

You can use this by using a new publishing method on a provider:

class SomeProvider:

    def boot(self):
        self.publishes({
            '/from/file': '/to/file'
        })

you can also tag this so you may want to group together multiple files under a namespace like views:

class SomeProvider:

    def boot(self):
        self.publishes({

            '/package/views/admin.html': 'resources/templates/vendor/admin.html',
            '/package/views/dashboard.html': 'resources/templates/vendor/dashboard.html',
            '/package/views/users.html': 'resources/templates/vendor/users.html',
            '/package/views/pages.html': 'resources/templates/vendor/pages.html',

        }, tag='views')

You can then use this by running a new publish command:

$ craft publish SomeProvider --tag views

[coveralls]

Coverage decreased (-0.03%) to 87.107% when pulling f1cfe14 on feature/534 into 10793e0 on develop.

[josephmancuso]

since migrations need special logic (create the file with the correct timestamp of right now) you need to run:

class SomeProvider:

    def boot(self):
        self.publishes_migrations([
            '/migration-directory/1',
            '/migration-directory/2'
        ], tag='some-tag')

[thetonus]

Use context managers