Rename features_exclude to features_ui_autodetect_exclude (less confusing) [#1990290]

Since playing with the new features_exclude I think I get the general concept of the functionality now but I think it could be named better. I propose we rename features_exclude to features_ui_autodetect_exclude.

Relevant issue discussed here -> #1978288: Features module .info file has "features_exclude" items vs "features" items for no apparent reason (fields can go "missing")

Comment	File	Size	Author
#1	features-rename-features-exclude-1990290-1.patch	3.58 KB	Elijah Lynn
#1

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Elijah Lynn

Portland, Oregon

CreditAttribution: Elijah Lynn commented 8 May 2013 at 16:43

File	Size
features-rename-features-exclude-1990290-1.patch	3.58 KB

Comment #2

Elijah Lynn

Portland, Oregon

CreditAttribution: Elijah Lynn commented 8 May 2013 at 16:43

Status:

Active

» Needs review

Comment #3

hefox CreditAttribution: hefox commented 8 May 2013 at 16:52

Renaming it will break existing features use of it, no?

The thing is that it's not just for auto-detect -- can manually add it if want to, just like can manually add components.

edit: what could be useful is adding a comment explaining why they were added to the .info file

Comment #4

Elijah Lynn

Portland, Oregon

CreditAttribution: Elijah Lynn commented 9 May 2013 at 15:24

Good point, didn't think about that. I was going off of:

The features_exclude lines are purely for the new UI to determine if an auto-detected dependency should be checked or if you have specifically unchecked it.

Source: http://drupal.org/node/1064472#comment-7196064

==============

That being said I would welcome a comment explaining this, I should be able to do this later today.