rdemetrescu

I'm having this issue as well. It seems to be a problem here: https://github.com/kevin1024/vcrpy/blob/c79a06f639dd628536c9868044e78df1012985f9/vcr/stubs/__init__.py#L230-L233 `filter_request` will call our own `before_record_response` where we could avoid modifying the response if we knew...

I use this monkey-patch on my projects: ```python from functools import lru_cache graphene.Enum.from_enum = lru_cache(maxsize=None)(graphene.Enum.from_enum) ```

> This problem is caused by multiple enum classes being created with the same definition. > Graphene sees them as different classes with the same name. > You can solve...

Any plans for fixing this issue? Will aurelia@next handle it correctly?