-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Consider impact of glint on API design #717
Comments
We're running into this introducing Glint to our codebase—we use |
I think we need to consider renaming and doing a major release. Any ideas on names? |
I'm wondering if there's a clear difference between the two: Could we use something like |
@swastik I'm OK with they proposed name change for the helper. We'll need a plan for migrating, deprecating, etc. |
Before glint/gts, having a modifier and helper with the same name didn't cause any issues, but it is a point of annoyance when working with glint. It's not a show stopper, because .gts file authors can easily alias the helper or modifier when importing it, but it would be good to consider a plan to evolve the addon to be more friendly in its default naming.
The text was updated successfully, but these errors were encountered: