option to disable guessers/loaders/voters globaly

[ElectricMaxxx]

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets	#242
License	MIT
Doc PR	symfony-cmf/symfony-cmf-docs#693

Started implementing with that and came to an easy global on/off/partial-off solution, we can start with. Doing some fance inheritance into the specific sitemap configurations will be an overkill atm - i think.

When you like that, i will do:

• configuration schema extension
• tests for configuration schema extension

[dbu]

for sitemap specific, we could have the same config in each configuration, and update the service tags with the sitemap attribute. but yeah, lets leave that out for now.

i would invert all and none, its confusing right now (the config does not say it would be about which services to skip). saying which to use, with default all sounds clearer to me.

i would make the configuration options arrayNode instead of comma separated. we can have a pre-task to convert a single string with "all" or also "...loader.phpcr" to an array.

i wonder if all/none could clash with a sitemap name. maybe use _all / _none? or something else that is very unlikely to be a sitemap? particularly all sounds a bit risky.

[dbu]

oh, and lets start a separate doc PR so we get the first one merged at some point...

[ElectricMaxxx]

@dbu as the issue starts with disable ... i implemented it from the position, which sitemaps to disable :-) but i can change it if you want to.

I started implementing the configuration as an enumNode, but had problems to describe the custom list as values :-( So you really want to blow up the Configuration.php just to get the list as a pre-task? I think i can devide the values better as strings, the list is just one of the possible options, and i would have to extract all/none when they are the values.

To set the same option into each sitemap would be not the problem, to disable the services for more then one sitemap, would be very hard. I would imagine to steel the service caused by the option on one sitemap and an other still whants the service ... So lets just keep it global for now.

[ElectricMaxxx]

@dbu i don't understand the thing with mixing sitemap names and all|none the options never touch a sitemap by its name. in the worst case a service with the id all|none can't be implemented.

[dbu]

i would just add that to the rest of the sitemap thing

[ElectricMaxxx]

@dbu we should merge that, right?

[dbu]

i squashed commits. i think its now ready to merge. i created a separate issue for the doc, so that we don't block the initial doc PR any longer.