lermontex
lermontex
Apparently, it will not be possible to completely get rid of the websocket yet. In addition, the current implementation in the api platform only supports update operations. https://github.com/api-platform/core/pull/3321 https://github.com/api-platform/core/issues/4302
Unfortunately, it didn't work ``` curl -X 'GET' \ 'https://localhost/api/users/01G1CJ7WF6B46AWM4EWTKZ1YM1/domains/01G1CJ7WF6B46AWM4EWTKZ1YM2/reset_token_requests?page=1' \ -H 'accept: application/ld+json' ``` `[Semantical Error] line 0, col 94 near 'user IN (SELECT': Error: Class App\\Entity\\ResetTokenRequest has no...
@mwierzbi no, unfortunately, due to the lack of documentation I had to abandon the idea of using my own uriVariables
Yes, I cleared the cache, but the problem is still there. I have added a repository to demonstrate this error: https://github.com/lermontex/api-platform-bug-example
I checked version [v2.7.0-beta.4](https://github.com/api-platform/core/releases/tag/v2.7.0-beta.4) - the bug is still there
@chalasr, @JorickPepin, @Jean85, > @EvilSpartans, you may want to add user_id_claim: email in the configuration file so that the name of the key in the token payload remains email and...
@Akryum the same issue with @vue/apollo-composable 4.0.1 and @apollo/client 3.9.5 The error disappears if you set `fetchPolicy: "no-cache"`, perhaps this can somehow help understand the reason for this behavior?
The same error with @intlify/unplugin-vue-i18n 0.8.2 ``` file:///srv/app/dist/server/entry-server.js:8 import { useI18n, createI18n } from "vue-i18n/dist/vue-i18n.runtime.esm-bundler.js"; ^^^^^^^^^^ SyntaxError: Named export 'createI18n' not found. The requested module 'vue-i18n/dist/vue-i18n.runtime.esm-bundler.js' is a CommonJS module,...
@alivadjid, The issue is with the Vite plugin `unplugin-vue-i18n`, not `vue-i18n`. The `unplugin-vue-i18n` plugin is optional for `vue-i18n`. You can import messages yourself, as described in the documentation. However, it...
I'm currently using Symfony 7.0.6 and api-platform/core v3.3.0-beta.1 and haven't noticed any breaking bugs when working with GraphQL (including Enum). Since the update was for testing purposes, I can continue...