Support multiple avro folders

[fmeurou]

When creating modules, I want to manage one avro folder per module, but the configuration does not allow this.

[lukaszb]

@fmeurou can you elaborate on your use case? What do you mean by "creating modules"? Do you maybe have some working code or will to prepare a pull request for the feature?

[fmeurou]

Hi Lukasz, As far as I understand, if I use several apps that have avro files on a project, I need to centralize all avro files for all apps in a specific place because the setting only allows me to define one place for avro files. If it was working like templates do, I'd be able to tell the project to look for avro folders in each module. Does it make sense ? Fred

…

-------- Original Message -------- Subject: Re: [ApplauseOSS/djangoevents] Support multiple avro folders (#37) Local Time: 13 November 2017 10:01 AM UTC Time: 13 November 2017 09:01 From: ***@***.*** To: ApplauseOSS/djangoevents ***@***.***> fmeurou ***@***.***>, Mention ***@***.***> ***@***.***(https://github.com/fmeurou) can you elaborate on your use case? What do you mean by "creating modules"? Do you maybe have some working code or will to prepare a pull request for the feature? — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#37 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AHbLIfccXAfHRJyPtUkV246ZVxqsPJMzks5s2AVggaJpZM4PgV-4).

[lukaszb]

Yeah, it does make sense. However, until now we've been using avro schemas against micro services and our aggregates were easily distinguished by name within single project. I understand that you want to somehow tell djangoevents to use avro schemas that are i.e. put into subdirectories of main schema dir or distributed within Python packages, right?

Looks like this can be quite easily accomplished with some custom schema loading mechanism. I.e. we could change djangoevents.schema.event_to_schema_path method to use some aggregate's/event's method that returns absolute path to the schema (and fallback to current behaviour).

So at the event you could do something like:

class Person(BaseAggregate):
    schema_dir = '/my-avro-schemas-dir'

    class Updated(DomainEvent):
        pass

Then you could probably prepare some base aggregate classes for each module.

This should be enough for most use cases I believe. Does it sound good or do you think of another solution? Would you like to prepare a PR for this?