Vale comments

Results 13 comments of


                                            Vale

Error when clicking on any sort of dropdown/select: TypeError: g.indexOf is not a function & react-error-boundary requires either a fallback

I'm facing the exact same problem, but in my case downgrading didn't work. In my case, I am using a generic `article` component in many content types (`articleA`, `articleB`, `articleC`...

[Bug] Revectorization on object batch without any change on the text to embed

Please note that it costs less than 0.01$ to reproduce

[Bug] Revectorization on object batch without any change on the text to embed

You're welcome @etiennedi, I'm happy to see progress on this issue :)

[gpg] Unable to init gpg identity

@cbouvet-ledger any idea ?

fix(type-safe-api): create a new asset with PrepareApiSpecOptions props and used it in PrepareApiSpecCustomResourceProperties instead or raw properties in order to avoid large payload that can cause the PrepareSpecCustomResource to fail

Hi @agdimech, Here is a pull request, I don't have any more time at the moment to work on it, I will test it tonight (in ~12h in my time...

fix(type-safe-api): create a new asset with PrepareApiSpecOptions props and used it in PrepareApiSpecCustomResourceProperties instead or raw properties in order to avoid large payload that can cause the PrepareSpecCustomResource to fail

I just tried but I got an error now when I run `pdk build` project on the `generate-license-file` step. This is the first time I got this error, I tried...

fix(type-safe-api): create a new asset with PrepareApiSpecOptions props and used it in PrepareApiSpecCustomResourceProperties instead or raw properties in order to avoid large payload that can cause the PrepareSpecCustomResource to fail

Thanks, I downgraded my version to node@20 and will stay on that version from now. It now builds as expected. I followed the [official documentation](https://aws.github.io/aws-pdk/contributing/index.html) in order to use my...

fix(type-safe-api): create a new asset with PrepareApiSpecOptions props and used it in PrepareApiSpecCustomResourceProperties instead or raw properties in order to avoid large payload that can cause the PrepareSpecCustomResource to fail

Hi @agdimech, I hope you're doing well. I wanted to follow up on my previous comment. I've been diving into the issue and think I might've stumbled upon a workaround...

fix(type-safe-api): create a new asset with PrepareApiSpecOptions props and used it in PrepareApiSpecCustomResourceProperties instead or raw properties in order to avoid large payload that can cause the PrepareSpecCustomResource to fail

Yes it's simpler to do that, it was just a proposition to move assets to separate buckets and to support history with a timestamp or datetime as a root folder....

fix(type-safe-api): create a new asset with PrepareApiSpecOptions props and used it in PrepareApiSpecCustomResourceProperties instead or raw properties in order to avoid large payload that can cause the PrepareSpecCustomResource to fail

I attempted with some changes, but now I encounter the same error with ApiOptionsDeploymentCustomResource859991B0: ``` 652317 byte payload is too large for the Event invocation type (limit 262144 bytes) (Service:...