Skip to content
This repository was archived by the owner on Nov 7, 2018. It is now read-only.

Add back Initialize #185

Closed
HaoK opened this issue Apr 20, 2017 · 4 comments
Closed

Add back Initialize #185

HaoK opened this issue Apr 20, 2017 · 4 comments
Assignees
@HaoK
Labels
3 - Done enhancement
Milestone
2.0.0-preview2

Comments

@HaoK
Copy link
Member

HaoK commented Apr 20, 2017

Add a Initialize<TOptions> set of actions which run after Configure, needed for Auth
@HaoK HaoK self-assigned this Apr 20, 2017
@HaoK HaoK added this to the 2.0.0 milestone Apr 20, 2017
@HaoK HaoK mentioned this issue Apr 26, 2017
Closed
@MaKCbIMKo
Copy link

A quick question: Why Initialize goes after Configure? Does it correlate with principle of least astonishment? By these names, seems like you need to initialize object first and then configure that.

@HaoK
Copy link
Member Author

HaoK commented Apr 27, 2017

Yeah its a naming issue, I'm open to considering different names if you have any ideas for something clearer that signify's happening after Configure.

@MaKCbIMKo
Copy link

I suppose, that just switch the names isn't option? :)

How about that:
First step - Configure is like a 'rough processing'.
Second step - Adjust or [Fine]tune for polishing (fine tuning, polishing)

@HaoK HaoK modified the milestones: 2.0.0-preview2, 2.0.0 May 15, 2017
@HaoK HaoK added the 3 - Done label May 15, 2017
@HaoK
Copy link
Member Author

HaoK commented May 15, 2017

52ab5f1

@HaoK HaoK closed this as completed May 15, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@HaoK HaoK

Labels
3 - Done enhancement
Projects
None yet
Milestone
2.0.0-preview2
Development

No branches or pull requests
2 participants
@HaoK @MaKCbIMKo