You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of the features we added here were only features / conditional because they were in-development and I often want to encourage people to work iteratively. Some features should eventually transition to be removed to reduce complexity and keep rules_ios lightweight
Because of this - we have some features that should be removed - and we have to maintain complexity while they stay around. My proposal is:
develop a feature - by adding --features apple.enable_awesome_feature
default the feature to enabled - and then
2a. if the feature isn't deemed ideal to keep around, then schedule it for removal.
2b. the feature scheduled for should follow Bazel's incompatible pattern - to encourage
people to flag issues with us.: apple.enable_awesome_feature -> apple.incompatible_disable_awesome_feature
Related is this thread about enabling defaults: #630
The text was updated successfully, but these errors were encountered:
A lot of the features we added here were only features / conditional because they were in-development and I often want to encourage people to work iteratively. Some features should eventually transition to be removed to reduce complexity and keep rules_ios lightweight
Because of this - we have some features that should be removed - and we have to maintain complexity while they stay around. My proposal is:
--features apple.enable_awesome_feature
2a. if the feature isn't deemed ideal to keep around, then schedule it for removal.
2b. the feature scheduled for should follow Bazel's
incompatible
pattern - to encouragepeople to flag issues with us.:
apple.enable_awesome_feature
->apple.incompatible_disable_awesome_feature
Related is this thread about enabling defaults: #630
The text was updated successfully, but these errors were encountered: