luckyframework / luckyframework/lucky_cli
Add configuration to disable forgery protection in the test environment
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 92
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Now that https://github.com/luckyframework/lucky/pull/1657 is merged, new projects should have CSRF protection turned off while running tests. We'll need to find the best place for it to live in the `config/` directory.
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 in the generated project's config/ directory and review the behavior introduced by luckyframework/lucky#1657. Identify where test-environment configuration is created, then verify that newly generated projects disable forgery protection while running tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100