Nope I want null, i.e. empty. "null" wouldn't fix...
# package-development
a
Nope I want null, i.e. empty. "null" wouldn't fix the issue further down the line where the C# side cannot find a publishedcontent due to the culture being "undefined", this would be the same as "null". Setting it as null (no quotes) solves the issue 🙂
j
They will both result in exactly the same thing being sent in the URL. It's just that
null
gets implicitly type converted to
"null"
when you do
"somestring" + null
My point is, because that's what's happening whether you do
null
or
"null"
, it would be better to be explicit.
a
Ohhh I get you 👍 Sorry front end isn't my favourite thing 😅
j
No worries.
a
Ah that didn't work:
It still comes over as a string, I want it to be nothing
j
oh, as in empty? ""?
a
Ha I feel so stupid, the fix was easy
needed to be = "" not = null