Jack Coy

Ahh, nice. Yeah seems likely! I look forward to updating and testing when the PR is merged.

Hey all 👋 I just wanted to confirm that we are still seeing this error. Here are the details for the latest reported error: ``` SyntaxError: Unexpected token . at...

Hi @silesky it appears that [the PR](https://github.com/segmentio/action-destinations/pull/943) you linked to earlier in this thread has turned out to not be the best approach to solving this issue. Do you have...

Hey @silesky thanks for the reply and insight. We are not in an enterprise environment and are hoping to avoid the ownership of the solution you suggested, but I do...

The ISSUE TEMPLATE link above is broken. Our scenario was somewhat tightly tied to our implementation, so it may take a bit of time to prepare a reproduction for you.

I am trying to upgrade to 5.x and am running into this issue as well. It's particularly frustrating because it is not specific about where the error occurred. We have...

Hello all, I am trying to get the following to work correctly, but unfortunately I receive an error during response validation when the value is `null`. ### This ```yaml type:...

@Tlepel So are you saying I need to add `null` in the enum list for my string type? If so, that doesn't feel quite right. The list of enum values...

@Tlepel I tried something similar to what you suggested as my enum was actually a `$ref`: ```yaml type: oneOf: - type: "null" - $ref: "schemas.yaml#/QuestType" ``` This required me to...

Hi @cdimascio @mdmower @SF97 I'm still looking forward to testing this as I think it will help with a number of issues I'm facing around `nullable`. Where are things at...