Skip to content

arguments for tasks? #9

Open
Open

Description

@sam0x17

This would be really nice to have.

Activity

  1. axvm commented on Aug 16, 2019

    @axvm
    Owner

    Hi @sam0x17
    Arguments should to be accessible via ARGV const

  2. axvm commented on Aug 16, 2019

    @axvm
    Owner

    Also I propose to you use ENV to define arguments like in rails.
    i.e. SOMEARG=123 cake :task_readinv_env
    This way is much better cuz it gives to user ability to chain tasks without passingthru args.
    But if you believe it shoud to be different - looking forward for your opinion. Im open for discussion about cake functionality.

  3. sam0x17 commented on Aug 18, 2019

    @sam0x17
    Author

    my use case is migrating to particular migration numbers, and a cake exec command that executes the input string as crystal code within the app environment and prints the result.

  4. sam0x17 commented on May 19, 2020

    @sam0x17
    Author

    ARGV comes up empty when read from within a task -- I'm guessing it is consumed by the cake binary

  5. axvm commented on May 19, 2020

    @axvm
    Owner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions