search

jnoellsch / ektron-fluentapi

Adds a fluent API over the existing Ektron Framework API to increase code readability and discoverability
MIT License
2 stars 0 forks source link

Namespace refactor #10

Open jnoellsch opened 9 years ago

jnoellsch commented 9 years ago

Leave as-is.

ssartell commented 9 years ago

I'd be okay with renaming. I don't particularly like the idea of putting anything in Ektron's namespace. Also should we split the mapping stuff from the fluent API?

jnoellsch commented 9 years ago

RE: Namespace – so what should it be?

RE: Splitting – to a different project or namespace?

From: Sean Sartell [mailto:notifications@github.com] Sent: Sunday, January 11, 2015 7:54 PM To: jnoellsch/ektron-fluentapi Cc: Jim Noellsch Subject: Re: [ektron-fluentapi] Namespace refactor (#10)

I'd be okay with renaming. I don't particularly like the idea of putting anything in Ektron's namespace. Also should we split the mapping stuff from the fluent API?

— Reply to this email directly or view it on GitHub https://github.com/jnoellsch/ektron-fluentapi/issues/10#issuecomment-69522901 . https://github.com/notifications/beacon/AJv_F9yXyl6oiFBXb_EuXo1gtgwXMboIks5ngyDPgaJpZM4DLX9v.gif

ssartell commented 9 years ago

Rightpoint.Ektron.Blah? Or we could come up with a name for this project.

jnoellsch commented 9 years ago

I guess it could be Rightpoint.Ektron but it felt weird tying code that we might want to “own” to a company.

From: Sean Sartell [mailto:notifications@github.com] Sent: Monday, January 12, 2015 9:12 AM To: jnoellsch/ektron-fluentapi Cc: Jim Noellsch Subject: Re: [ektron-fluentapi] Namespace refactor (#10)

Rightpoint.Ektron.Blah? Or we could come up with a name for this project.

— Reply to this email directly or view it on GitHub https://github.com/jnoellsch/ektron-fluentapi/issues/10#issuecomment-69583683 . https://github.com/notifications/beacon/AJv_Fys3Qc18KZNkdmiJpeU6LSQkx4Owks5ng9vGgaJpZM4DLX9v.gif