luckyframework / luckyframework/habitat
Problems with accessing settings within ECR
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 83
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
I used Lucky Jumpstart to get up and running with a new app.
It creates a habitat config for application configuration and one place that it uses it is in the sign up confirmation email. I was testing out Breeze's carbon extension and notices that the application name wasn't showing up in the body of the email though it was showing up in the other places it was used.
I think there might be an issue with how ECR templates are loaded and the way habitat works.

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the missing application name with the Lucky Jumpstart sign-up confirmation email, using the linked html.ecr template and Breeze's carbon extension. Trace how the habitat setting is accessed while that ECR template is rendered. Done means the application name appears in the email body as it does in the other referenced locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100