Skip to content

CLI should be more strict with function names #503

Open

Description

@delabassee

fn init doesn't test if a function name has space(s) in its name or if the name starts/end with a separator(s).

Ex. the following functions will be successfully bootstrapped by init but will fail at the build stage given their names doesn't comply with Docker naming convention.

fn init --runtime go "  "
fn init --runtime go "john doe"
fn init --runtime go "...."
fn init --runtime go .separator
fn init --runtime go separator.

and with other separators : -, _,--, __

Activity

  1. changed the title [-]CLI should be more strict about function names[/-] [+]CLI should be more strict with function names[/+] on Dec 19, 2018
  2. self-assigned this
    on Mar 1, 2019
  3. added 2 commits that reference this issue on Mar 1, 2019
    634aafe
    ed04195
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions