https://prefect.io logo
j

Joish

07/08/2023, 7:45 AM
#prefect-cloud I am not able to enter values in my cloud ui Has anyone faced this or am I doing some mistake.
c

Christopher Boyd

07/08/2023, 12:14 PM
It’s looking for valid JSON, which should be like [“value”] or {“json”: test}
What happens when you do that
“Ooouio” would be just a string
j

Joish

07/08/2023, 12:26 PM
yes it is looking for a valid JSON "something" is also a valid JSON i mean, why should it be in a array..?
c

Christopher Boyd

07/08/2023, 12:27 PM
It’s looking for an object
Can you test with [] and or {} anyways just to confirm ?
j

Joish

07/08/2023, 12:30 PM
i mean it will work with [], but I have to change the code to access elements from the array also, it was working like yesterday
as in this "something"
c

Christopher Boyd

07/08/2023, 12:33 PM
What happens if you paste it in and not type it in - does that work ? Also - we reported https://github.com/PrefectHQ/prefect-ui-library/issues/1558 and I can raise this internally
Can you share a snippet of code where this parameter is defined so I can test it ?
j

Joish

07/08/2023, 12:36 PM
yes, i did try to paste it, but the min i paste the string the double quotes vanish
c

Christopher Boyd

07/08/2023, 12:41 PM
I can look at it - from what I can tell you’re not coercing any types here so Prefect is assuming it’s json
Realistically this is just a string right ?
j

Joish

07/08/2023, 12:43 PM
yes
let me do that
c

Christopher Boyd

07/08/2023, 12:48 PM
This lets me put “test” by type hinting it -
j

Joish

07/08/2023, 12:52 PM
one question here regarding
I can look at it - from what I can tell you're not coercing any types here so Prefect is assuming it's json
let it assume as json "test" is a valid JSON so what is the problem in that..? Also, why does the double quotes vanish
c

Christopher Boyd

07/08/2023, 12:58 PM
I think the issue is in the JSON formatter - in order to display and detect what is / isn’t valid json and syntax hifhlighting, it’s needs to escape what you have . I think the expectation and anticipation is that “this” is a string while {“this”} is Json. I can raise this thread up in that ticket I shared earlier if you’d like - I don’t know enough about how it’s written in the UI to know what the expectation is here in totality - e.g is this an unintended bug and we should accept “test” as an input , or is this a design constraint that we are not intentionally, and if so we need to be clear what inputs are accepted
I take your point and will bring it up to the team , the short answer is I don’t know
j

Joish

07/08/2023, 1:01 PM
thanks for your time and help yes, can you raise this point with your team and update me on this please thanks once again
👍 1
1
c

Christopher Boyd

07/08/2023, 1:14 PM
I updated the issue with this report thank you for sharing
j

Joish

07/09/2023, 8:00 AM
thank you for resolving it soon