Alessio Gravili comments

Results 104 comments of


                                            Alessio Gravili

CMS thinks content has changed

![Arc 2023-04-08 at 00 53 39@2x](https://user-images.githubusercontent.com/70709113/230689654-2c85be0d-f0d2-4905-88b4-e30c53fb9dd1.jpg) The error popup is there actually - just at the completely wrong position. Whoops! Will fix!

CMS thinks content has changed

> Setting validation "required" works since 0.1.2 (however without showing where the error happend - you probably misses the error popup in your custom field) Just fixed the error popup...

Renaming a pasted link also modfies the link itself

I think this is related to this comment: https://github.com/facebook/lexical/pull/4203#issuecomment-1484999459 Will work on fixing that!

Including getPayloadHMR in a NextJS app increases the bundle size significantly

This has been fixed by https://github.com/payloadcms/payload/pull/7620

dependency issue using localAPI in a sveltekit application

Fixed by https://github.com/payloadcms/payload/pull/7620

[WEB-995] Support tsconfig `nodenext`

Would be great if this could be added soon! Can't wait to cut my compile times in half. At [payload](https://github.com/payloadcms/payload/blob/beta/tsconfig.json) we LOVE supporting the latest and greatest next features. And...

Windows only: `generate:types` not working properly

Thank you! This has been fixed in https://github.com/payloadcms/payload/pull/6804 and will be available in the next beta release (today) :)

lexicalEditor - localized richText in a BlocksFeature does not get returned from the API

Fixed in #6489. Fields no longer get omitted from the API response. Proper localization support will be worked on soon

Localized text is not saving with lexical rich text editor and Postgres (payload and @payloadcms/* beta 10, next 14.2.0 stable)

Good chance this is a lexical issue, yep! Lexical currently does not handle localization nicely, will work on that tomorrow

Localized text is not saving with lexical rich text editor and Postgres (payload and @payloadcms/* beta 10, next 14.2.0 stable)

Hey @BohdanK-W32 So Lexical does have issues with localized SUB-Fields. E.g. if you have a lexical blocks feature with localized fields, those are currently treated as if they are unlocalizd....