Skip to content

Update documentation to describe ArrayChoiceList usage #5405

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

Closed
ryanotella opened this issue Jun 16, 2015 · 4 comments
Closed

Update documentation to describe ArrayChoiceList usage #5405

ryanotella opened this issue Jun 16, 2015 · 4 comments

Comments

@ryanotella
Copy link

For users upgrading from 2.3 to 2.7, there are a lot of deprecation warnings around ChoiceList, SimpleChoiceList and ChoiceListInterface. The recommendation is to use ArrayChoiceList instead. However, there currently isn't any documentation about how to use that, and the current 2.7 documentation suggests using the deprecated ChoiceList. See http://symfony.com/doc/current/reference/forms/types/choice.html#choice-list

This is a very complicated area of Symfony forms which has been in a bit of flux due to potential API changes, so it would be good to have some examples of usage.

I'd update the docs myself, but I haven't figured out how ArrayChoiceList actually works yet.

@xabbuh
Copy link
Member

xabbuh commented Jun 16, 2015

@ryancastle Thanks for mentioning this. However, I will close here though as we are already aware of this (see #5179). Anyway, thanks again. :)

@xabbuh xabbuh closed this as completed Jun 16, 2015
@ryanotella
Copy link
Author

Yeah. Fair enough. I didn't find that one.

@adamelso
Copy link
Contributor

I've been looking through all the resources I can find... Symfony Docs, Symfony News posts, UPGRADE.mds, the source code, GitHub issues linked from here and others, StackOverflow, to name a few.

However, I am still not 100% certain what the upgrade course is for replacing the deprecated ObjectChoiceList with ArrayChoiceList.

As far as I can see, #5876 does not cover this issue which was meant to replace the closed #5179.

@HeahDude
Copy link
Contributor

Hi @adamelso, see #6393. Hope that helps.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants