luckyframework / luckyframework/carbon

The layout filename should include the content type

Open
#77 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Crystal
Stars
87
Forks
20
PR merge metrics
No merged PRs in 30d

Description

https://github.com/luckyframework/carbon/blob/61e75c5af460fa869278ae0cfedd587e2d6f9bd0/src/carbon/email.cr#L60

Related: https://github.com/luckyframework/carbon/issues/76

Instead of generating layout.ecr, it should look more like layout.html.ecr; however, if we change the naming, then this really become layout/your_layout_name.html.ecr

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/carbon/email.cr around line 60 and review related issue #76 for the naming context. Trace how the layout filename is generated, then verify that generated layouts include the content type and preserve the layout name path described in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
crystal
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.