You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where I'd like to use customFieldsPD. However, the documentation for that field makes it clear that the field has some deeply magical stuff going on, and shouldn't be trusted. My question is: is there any use case under which it's safe to use that field? For example, is there a guarantee that if I use parsePackageDescription and then use customFieldsPD on those results that I'll get the fields I'm looking for?
The text was updated successfully, but these errors were encountered:
I've not found nothing in docs about custom fields so i am not sure if the warning is there anymore.
However iirc there are some actual usages and the question were not answered so i guess we can close this, feel free to reopen on toher case
I have a use case where I'd like to use
customFieldsPD
. However, the documentation for that field makes it clear that the field has some deeply magical stuff going on, and shouldn't be trusted. My question is: is there any use case under which it's safe to use that field? For example, is there a guarantee that if I useparsePackageDescription
and then usecustomFieldsPD
on those results that I'll get the fields I'm looking for?The text was updated successfully, but these errors were encountered: