Hey, we’re currently migrating to Ash 3.0, which takes some time in our case (it’s a rather big project), so I won’t be able to run it on the main soon. I’m not sure when the migration will be done, but I’ll let you know ASAP if this is still an issue.
Anyways I was wondering if this is something that could be fixed as a part of Ash 2.0 support you’ve mentioned here Ash Framework 3.0
