Skip to content

Combine config into single config prop - #71

Closed
cookpete wants to merge 1 commit into
masterfrom
single-config-prop
Closed

Combine config into single config prop#71
cookpete wants to merge 1 commit into
masterfrom
single-config-prop

Conversation

@cookpete

@cookpete cookpete commented Jun 1, 2016

Copy link
Copy Markdown
Owner

I don't like how we have to carry around four separate config props in several places, especially for props that I think aren't used that often. This consolidates all the players' configuration data into one config prop, which falls back to a defaultConfig object for any property that isn't specified.

Still not sure if this is better than the current way of doing things. I'm happy to hear feedback if anyone has any.

This is definitely a breaking change and perhaps should wait until we're ready for a v1.0 release.

@cookpete cookpete added this to the v1.0 milestone Jun 1, 2016
@cookpete
cookpete force-pushed the single-config-prop branch from db1730d to 9dd7ab3 Compare July 30, 2017 17:23
@cookpete
cookpete force-pushed the single-config-prop branch from 9dd7ab3 to c81b7f2 Compare July 30, 2017 17:24
@cookpete cookpete closed this in 120d2db Sep 9, 2017
@cookpete cookpete removed this from the v1.0 milestone Sep 9, 2017
@cookpete
cookpete deleted the single-config-prop branch September 9, 2017 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant