luckyframework / luckyframework/lucky_cli

`lucky` should check crystal version in shard.yml before running tasks

Open
#341 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
92
Forks
48
PR merge metrics
No merged PRs in 30d

Description

That way it is clear when you have a version mismatch. Should raise if using incorrect version

We'd probably want some kind of `check_crystal_version` around here: https://github.com/luckyframework/lucky_cli/blob/e013182b48a74ac6b609a2daed7ac0156efdaaec/src/lucky.cr#L26

That checks for version mismatch. It should also be disable-able with an ENV var. Like `SKIP_VERSION_CHECK=true lucky my.task`

**It ideally check for a version control software and tell you how to install/switch to a different version.** For example, if `crenv` is installed, show what commands to run. Make it easy

If no crystal version manager software is found, suggest crenv of asdf and point to install page so they can use a version manager

Contributor guide

Open the contributing guide

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 at the version-check entry point in src/lucky.cr around line 26 and inspect how the project's shard.yml declares the Crystal version. Define the behavior for mismatches, the SKIP_VERSION_CHECK=true override, and guidance for crenv or asdf; done means the task stops with clear actionable output when the version is wrong and can be explicitly skipped.

Written by the indexing model from the issue text.

Assessment

Tech stack
crystal
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.