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

Already on GitHub? Sign in to your account

ParamConverter priority too high? #246

Closed
ghost opened this Issue Sep 23, 2013 · 3 comments

Comments

Projects
None yet
1 participant
@ghost

ghost commented Sep 23, 2013

Hi,
is there a reason why ParamConverter is set with the max priority allowed?

This way it is not possible to write custom ParamConverters for Propel Models.

Member

jaugustin commented Sep 23, 2013

I don't think there is any reason for that.
You could use named paramConverter to overwrite PropelParamConverter

@ghost

ghost commented Sep 23, 2013

I know I could use named paramConverter but that way I can't omit the @paramconverter annotation.

Member

jaugustin commented Sep 23, 2013

@andrea-chris I don't see any limit on priority I think you could set 100000 if you want ;)

jaugustin added a commit to jaugustin/PropelBundle that referenced this issue Sep 23, 2013

feat(ParamConverter): add named ParamConvert
this allow the PropelParamConvert to be used by name "propel"
Priority also lowered from maximum 10 to 1 #246

@havvg havvg closed this in #247 Sep 25, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment