Titanium JIRA Archive
Alloy (ALOY)

[ALOY-1498] Add ability to create new alloy app from apps other than builtin sample apps

GitHub Issuen/a
TypeNew Feature
Priorityn/a
StatusOpen
ResolutionUnresolved
Affected Version/sn/a
Fix Version/sn/a
Componentsn/a
Labelsalloy, cli, samples, templates, titanium
ReporterBrenton House
AssigneeFeon Sua Xin Miao
Created2016-05-03T21:50:27.000+0000
Updated2016-05-11T18:35:41.000+0000

Description

{quote} As a developer, I want to be able to create a new Alloy app from a template other than the builtin Alloy sample apps, So that I can save development time and errors when creating apps that need to conform to corporate (or other) standards. {quote} Currently, as a developer, I can create a new Alloy app using
appc alloy new . --testapp NAME_OF_SAMPLE_APP
The sample app must exist in the alloy\samples\apps directory. It would be nice to be able to point add other folders to this, perhaps in a similar way to ti config (paths.commands, paths.hooks, paths.plugins, etc) Maybe there could be a paths.samples property that could be used by developers to add other sample directories to be searched when using the --testapp parameter.

Comments

  1. Stephen Feather 2016-05-04

    Alloy should reference the paths.templates setting from the cli's config.json See TIMOB-16620 Most likely resolved with a unified cli/alloy tooling.
  2. Sharif AbuDarda 2016-05-06

    Hello [~brentonhouse], Can you follow [~sfeather] comment, see if that helps you? Thanks.
  3. Brenton House 2016-05-08

    I believe he was referring to a proposed code change to Alloy. I don't think Alloy currently references paths.templates.
  4. Brenton House 2016-05-11

    Wouldn't this issue be part of the Alloy CLI and not the Titanium CLI?

JSON Source