rtek
rtek
Jumping in on this since I found this same behavior while evaluating vue and distilled it down to this contrived example. https://stackblitz.com/edit/vite-auuvqt?file=src%2Fcomponents%2FWrapper.vue There is something about looping over `useSlots().default()` that's...
Here is a workaround, for what its worth. Add this to your config file. ``` services: 'goetas_webservices.xsd2php.naming_convention': public: true class: '\My\NamingStrategy' ```
@lingosandi the `vue3-bug-example` repo is missing the source. I might be having the same issue demoed at https://stackblitz.com/edit/vite-auuvqt?file=src%2Fcomponents%2FWrapper.vue
Please come up with a more reasonable way to handle deprecation of the runners. Consider how AWS handles lambda runtime deprecations as an example. They distribute emails when old runtimes...
Great. I submitted one for the Guzzle client but the CI failed because of the key settings. Could you recommend what I should do there? Locally I fudged the a...
We're experiencing significant performance issues with the cell merging after moving from 1.24 to 1.25. Approximately a 10 increase in spreadsheet generation that requires multiple merges of blank cells. An...
Ah understood. Is the performance issue due to using the calculated value instead of the raw value for populating the left most cell?
Inline hack that I used to get `fetchAll` working for the `listRepositories` command. Mileage may vary. ```php $pager = new class($client) extends ResultPager { protected function callApi(ApiInterface $api, $method, array...
This along with all the other php8.1 related deprecations need to be merged.
Id go with option 2 as the list can get very long. May I request that $code is validated against possible values as well?