Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generalize DI using AnnotatedFunction #31

Merged
merged 11 commits into from
Feb 16, 2015
Merged

Conversation

ludovicc
Copy link
Collaborator

Solves #25

@jokade
Copy link
Owner

jokade commented Feb 15, 2015

@ludovicc Great work!
Could you please give me a short summary of the changes regarding AnnotatedFunction along with some use cases (so that I can update the README)?

On a side note, I have redesigned the directive API, since using a scala classes for directive controllers doesn't work out (the controller instance is created by Angular). I would be glad if you could give me your opinion on this -- the changes are located in the issue28 branch.

I hope that we can publish a 0.2 release within the week.

@jokade
Copy link
Owner

jokade commented Feb 15, 2015

I have one minor concern regarding your refactoring: a value named angular within the package object angular could result in confusing compiler errors, if one imports biz.enef.angular instead of biz.enef.angular._. Maybe we should rename the Angular trait to NGand then use Angular as the name of the value in the package object? Another option would be to rename the entire package to ng (but that's a quite extensive change for such a minor issue).

@ludovicc
Copy link
Collaborator Author

Hi,

Good pick!
I would rename the whole package to 'angulate', since that's the name of
the library.

Otherwise, rename the angular value to 'ng'.

Ludovic

On 15/02/2015 14:30, jokade wrote:

I have one minor concern regarding your refactoring: a value named
|angular| within the package object |angular| could result in confusing
compiler errors, if one imports |biz.enef.angular| instead of
|biz.enef.angular._|. Maybe we should rename the |Angular| trait to
|NG|and then use |Angular| as the name of the value in the package
object? Another option would be to rename the entire package to |ng|
(but that's a quite extensive change for such a minor issue).


Reply to this email directly or view it on GitHub
#31 (comment).

@ludovicc
Copy link
Collaborator Author

On 15/02/2015 13:18, jokade wrote:

@ludovicc https://github.com/ludovicc Great work!
Could you please give me a short summary of the changes regarding
|AnnotatedFunction| along with some use cases (so that I can update the
README)?

On a side note, I have redesigned the directive API, since using a scala
classes for directive controllers doesn't work out (the controller
instance is created by Angular). I would be glad if you could give me
your opinion on this -- the changes are located in the |issue28| branch.

I hope that we can publish a 0.2 release within the week.


Reply to this email directly or view it on GitHub
#31 (comment).

I have documented AnnotatedFunction in the Readme.

jokade added a commit that referenced this pull request Feb 16, 2015
Generalize DI using AnnotatedFunction
@jokade jokade merged commit dd46582 into jokade:master Feb 16, 2015
@jokade
Copy link
Owner

jokade commented Feb 16, 2015

Sorry, I didn't notice that your changes to the Readme...
I went ahead and renamed the base package to angulate.

@ludovicc
Copy link
Collaborator Author

Thanks for merging. I'm still reading about directives in Angular, I'll try to have some feedback by the end of the week.

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.

2 participants