-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Replace Teeplate with LuckyTemplate #1861
Conversation
# Doing this because `component_class` will raise an exception if the value is missing | ||
# but the error message would say "component_class is missing" which isn't as nice of | ||
# an error message. This lets the UI remain the same until this whole deal can be refactored | ||
component_class | ||
nil | ||
rescue | ||
"Component name is required." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is mainly just to keep the output the same as it is now. I have an issue on LuckyTask luckyframework/lucky_task#8 so we can address this later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I totally forgot about this
Purpose
Fixes #1832
Ref #1746
Description
We originally used Teeplate for all of the tasks that generate files. It was a good template system, but it doesn't really work on Windows. We now have LuckyTemplate which does work on Windows. By migrating this system over, this will bring Lucky to Windows compatibility 1 more step closer.
Checklist
crystal tool format spec src
./script/setup
./script/test