Abdón Rodríguez
Abdón Rodríguez
@danielroe > It might be worth considering enabling runtime compilation of templates via opt-in - what do you think @pi0? @pi0 > Enabling the opt-in option to use runtime compiler...
> And the link in the previous comment is now dead. Any suggestions about what to use instead? You can try this: https://github.com/IBM/pwa-lit-template
My thought is to comply the semver, not the Polymer versions. So... - `PSK ^1.0.0` is built in Polymer v1 with gulp tasks. - `PSK ^2.0.0` is built in Polymer...
Right! With this query: ```graphql { battles { id videos_func { count } } } ``` The response is: ```json { "errors": [ { "message": "An unexpected error occurred.", "extensions":...
Just with the query: `POST /graphql` Payload: ``` {"query":"{\n battles {\n id\n videos_func { count }\n }\n}","variables":null} ```
Yes, no custom hooks / flows related to this query.
Right, in my matchdays and battle collections I have the status field. And in the permission I required to published. The videos has no status field.
If I miss something and I should do the query in another way, any help will be welcome!
> Odd! Looks like the nested `profiles_id.id` is seen as a String rather than an ID. Exactly... > Just to make sure: the `profiles_id` field of `matchdays_participants` is a many...
Thanks for working on this! We also have this problem.