Miro Yovchev

I fully understand. I've just officially entered beta (like minute ago) and the tasks in order to enter stable are not fitting the screen (it's a quite big screen :)...

I was about to mention that "changing my mind" on locale support/auto publish is a big deal for me. I'm currently in re-iteration which may brings some changes to our...

Completely agree about the redundancy. If the filter provided is part of the schema, there is no need re-enter the details (except when in a need of override). This issue...

I'd like to share my thoughts about this. I've used the `nestedModuleSubdirs: true` feature of a2 in my first project and I loved it! It really helps you organize your...

Just to be sure about it - `@orgname/modulename` as a local module (application level) without corresponding (installed) npm module should work fine?

> It would work yes. :partying_face: > You should register the corresponding npm organization so you have the option of publishing that module in future. Yep, I'm aware of that....

@boutell I think I'm witnessing the same behavior (console warning) without any custom projections but using the piece built in relation filter (think of articles filtered by a tag). The...

@boutell https://github.com/myovchev/apos-issue-3626 Ccreate an article, assign a tag, create and navigate to an article page type, click the tag, logout and look at the console logs.

Just to add more context - I was using `archived` as boolean in a piece. I got a very long scary error trace on piece create claiming the system can't...

I'm not sure how well this would work with external systems when consuming the apos API. I really prefer `422 Unprocessable Entity` error thrown to a client which is not...