-
Notifications
You must be signed in to change notification settings - Fork 501
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
angular module: Move options into single attribute and provide it as json #47
Comments
I appreciate this approach as we already discussed. Defining the options in a controller seems more convenient to me than the css-style version that has to be parsed when the module is initialized. |
hi! this proposed structure is exactly what iam searching for! +1 options would be more flexible and reusable ... |
I made this change locally, works great for my purposes. But if you release a version with this feature, I'll update to that release. |
@thelarz the community and the repository would benefit by you opening a pull request with your changes |
I'd be glad to. Check my work, I'm no JS guru. |
Can you please open a pull request or tell me where to find your code. Never mind, no one needs to be a guru to make a meaningful contribution ;) |
added to development branch: #51 and will be released in 2.1.0 |
Sorry, out of pocket today but I'm anxious to get this going. I had to Sent from my iPhone On Oct 18, 2013, at 8:41 AM, Robert Fleischmann notifications@github.com Can you please open a pull request or tell me where to find your code. — |
We should provide the options format for the angular module as JSON format in a separated attribute to be more conventional. That also will solve issues like referencing to variables (#44).
Example for easy-pie-chart:
A way better:
What do you think about it ?
The text was updated successfully, but these errors were encountered: