Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

customFieldsPD #2585

Closed
snoyberg opened this issue May 8, 2015 · 2 comments
Closed

customFieldsPD #2585

snoyberg opened this issue May 8, 2015 · 2 comments

Comments

@snoyberg
Copy link
Collaborator

snoyberg commented May 8, 2015

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?

@23Skidoo
Copy link
Member

23Skidoo commented May 8, 2015

/cc @dcoutts

@jneira
Copy link
Member

jneira commented May 11, 2022

We are talking about:

customFieldsPD :: [(String,String)], -- ^Custom fields starting
-- with x-, stored in a
-- simple assoc-list.

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

@jneira jneira closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants