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

Do not override SimpleFormatter::format to use processCollection #668

Closed
wants to merge 875 commits into from

Conversation

soullivaneuh
Copy link
Contributor

Fixes #667.

In a nutshell, format methods are not overriden anymore to take profit of processCollection method.

Rendering method just returns the data output.

Not sur if it's the good way but works and solve my issue.

Feel free for remarks and suggestions.

willdurand and others added 30 commits July 9, 2014 10:29
Sometimes instead real class name we can use custom handler name. Then this class can't be initialized and we will get this exception ```ReflectionException: Class custom_handler_name does not exist```
Don't parse custom properties as classes.
Add abstract="true" to abstract_formatter in container definition
Fix an error when trying to use embedded form collections.

Referenced issue: nelmio#442
Fix embedded collection of custom FormType Error
Unified data types [actualType and subType]
Updated tests.
JMS parsing fixes; updated {Validator,FormType}Parser, FOSRestHandler, and AbstractFormatter, and updated DataTypes enum.
Modified dataType checking.
Updated tests.
Updated DataTypes enum.
Quick fix and added doc comments.
CS fixes.
Refactored FormTypeParser to produce nested parameters. Updated tests accordingly.
Logical and CS fixes.
Sub-forms and more tests.
Logical and CS fixes.
Swagger support: created formatter.
Configuration and resourcePath logic update.
ApiDoc annotation update. Updated formatter and added tests.
Parameter formatting.
Added tests for SwaggerFormatter.
Added  option in annotation, and the corresponding logic for parsing the supplied values and processing them in the formatter.
Routing update.
Updated tests.
Removed unused dependency and updated doc comments.
Renamed 'responseModels' to 'responseMap'
Update the resource filtering and formatting of response messages.
Updated check for 200 response model.
Ignore data_class and always use form-type to avoid conflicts.
Fix: add 'type' even if '' is specified.
Refactored responseMap; added parsedResponseMap. Added tests and updated some.
Fix: add 'type' even if '' is specified.
Initial commit of command.
Finished logic for dumping files.
Updated doc comment; added license and added more meaningful class comment.

Array of models support.
Unified data types [actualType and subType]
Updated tests.
JMS parsing fixes; updated {Validator,FormType}Parser, FOSRestHandler, and AbstractFormatter, and updated DataTypes enum.
Modified dataType checking.
Updated tests.
Updated DataTypes enum.
Quick fix and added doc comments.
CS fixes.
Refactored FormTypeParser to produce nested parameters. Updated tests accordingly.
Logical and CS fixes.
Sub-forms and more tests.
Logical and CS fixes.
Swagger support: created formatter.
Configuration and resourcePath logic update.
ApiDoc annotation update. Updated formatter and added tests.
Parameter formatting.
Added tests for SwaggerFormatter.
Added  option in annotation, and the corresponding logic for parsing the supplied values and processing them in the formatter.
Routing update.
Updated tests.
Removed unused dependency and updated doc comments.
Renamed 'responseModels' to 'responseMap'
Update the resource filtering and formatting of response messages.
Updated check for 200 response model.
Ignore data_class and always use form-type to avoid conflicts.
Fix: add 'type' even if '' is specified.
Refactored responseMap; added parsedResponseMap. Added tests and updated some.
Fix: add 'type' even if '' is specified.
Initial commit of command.
Finished logic for dumping files.
Updated doc comment; added license and added more meaningful class comment.
Array of models support.
@soullivaneuh
Copy link
Contributor Author

@willdurand done.

@willdurand
Copy link
Collaborator

Looks like it broke several tests.

@soullivaneuh
Copy link
Contributor Author

Sigh, was not. :-(

I'll take a look later.

@soullivaneuh
Copy link
Contributor Author

@willdurand Should be OK now. 👍

@soullivaneuh
Copy link
Contributor Author

@willdurand I don't understand the failures, I can't reproduce it on local...

@willdurand willdurand added this to the 2.11.0 milestone Nov 10, 2015
@soullivaneuh
Copy link
Contributor Author

ping @willdurand. Any idea?

@willdurand
Copy link
Collaborator

I'll give it a try. I'd like to ship 2.11.0 by the end of this week.

@willdurand willdurand modified the milestones: 2.12.0, 2.11.0 Dec 3, 2015
@willdurand
Copy link
Collaborator

changed the milestone to get symfony 3.0 support first.

@soullivaneuh
Copy link
Contributor Author

Hey @willdurand! What should we do for this PR now? :-)

@soullivaneuh
Copy link
Contributor Author

@GuilhemN Well, maybe could you please give some details of why you closed this PR?

Thanks.

@GuilhemN
Copy link
Collaborator

Github closed it automatically because I changed the master branch.
Feel free to reopen it of course ;)

@soullivaneuh soullivaneuh changed the base branch from master to 2.x February 26, 2018 09:49
@soullivaneuh soullivaneuh deleted the process-collection branch February 26, 2018 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.