Tim Nagel merk

Organizations

FriendsOfSymfony ozfortress Infinite Networks discutere
Tim Nagel

Sorry I'm not sure. I dont use the serializer. If not I'm happy to accept a PR enabling this if it isnt already possible.

Tim Nagel

If you define the mapping in fos_elastica in your config.yml file as the proper type ElasticSearch will coerce the type correctly regardless of if …

Tim Nagel

I have sent a PR that lets you set property_path: false on a defined mapping property so it will not be automatically calculated.. #794 If you coul…

Tim Nagel
LogicException You can't advance the progress bar past the max value.
Tim Nagel

There is a compatibility problem with symfony 2.5 and this bundle's unstable 3.1-dev branch. Either upgrade to symfony >= 2.6 or downgrade this bun…

merk commented on pull request FriendsOfSymfony/FOSElasticaBundle#799
Tim Nagel

We encounter the same problem and I havent come up with a solution except thinking about storing what we miss while reindexing and go back and rein…

Tim Nagel

Propel support is no longer maintained. Unless someone using it provides PRs for updates it will remain as is.

Tim Nagel

Does your custom transformer get called? Can you put a var_dump or xdebug_break call inside and see that the $document is actually made?

Tim Nagel

Closing as it is already being discussed here: #793

Tim Nagel
LogicException, Progress Bar in the command line
Tim Nagel

Im sorry, I'm not following what the problem is here for you @gxolin - Can you please provide more information about what you're expecting and what…

merk commented on pull request FriendsOfSymfony/FOSElasticaBundle#799
Tim Nagel

It looks the reset problem was resolved in 3.1-dev where we dont run postPopulate for an individual type population: https://github.com/FriendsOfSy…

merk commented on pull request FriendsOfSymfony/FOSElasticaBundle#799
Tim Nagel

Your proposed changes in #797 and here regarding not running postPopulate unless --no-reset is present doesnt make sense to me: why would you popul…

merk commented on issue ruflin/Elastica#789
Tim Nagel

Sorry, I equate develop branch with master in my head - we're on the same page :)

merk commented on issue ruflin/Elastica#789
Tim Nagel

The way I like to work for development is to have a stable release branch where no new features go - but bug fixes do, and a development branch whe…

merk commented on issue ruflin/Elastica#789
Tim Nagel

Using a deprecation cycle during 2.0 and removal in 3.0 could work. I have a few things that I hope to propose over the next few months that are go…

merk commented on issue ruflin/Elastica#789
Tim Nagel

Not normally for dev no - for example FOSElasticaBundle has 2 branches right now: master, for developing 3.1, and 3.0 for bug fix releases to 3.0 (…

Tim Nagel
FOSCommentBundle maintainer
Tim Nagel

I have added @XWB to the FOS organisation. Welcome aboard!

merk commented on issue ruflin/Elastica#789
Tim Nagel

I'd be creating a 1.4 branch for maintenance of 1.4 and putting 2.0-dev into master personally though.

merk commented on issue ruflin/Elastica#789
Tim Nagel

I'd keep your tag format the same as for the 1.x releases (with or without a v) As for branches my personal opinion is 1.4, 2.0, 2.1, etc

merk commented on issue ruflin/Elastica#789
Tim Nagel

There isnt a hard link between Elastica's basic querying support and ElasticSearch versions, and you cant generally expect to use a feature in Elas…

merk commented on issue ruflin/Elastica#789
Tim Nagel

I'm completely +1 on semantic versioning. I dont believe being linked to ElasticSearch's version makes all that much sense now that the API is mor…

merk commented on pull request symfony/symfony#12528
Tim Nagel

:+1: - I have just encountered this issue where I wish to display validation failures from the bound object when the form is initially displayed. @bwo…

Tim Nagel

the use_alias is generally the problem here, --no-reset is not necessary when it is set but there is a problem with the IndexAlias handling if my_i…

Tim Nagel
Question: Sorting collection items
Tim Nagel

You can do this by providing a custom getter on your object and using property paths to access that getter instead of the default getter.