User story

As a developer, I want the correct variabel to be used in serialization.config so that the serialized items end up in the correct folder.

Expected behavior

The serialized items should end up in the foundation/feature/project folder.

Actual behavior

The sc-variable thats being used is now hard coded to $(featureFolder). It should depend on the layer that's selected by the user.

Steps to reproduce the behavior

yo helix:add
Select Project as layer.

The following is in the generated serialization.config file :

<targetDataStore
            physicalRootPath="$(featureFolder)\Login\$(configurationFolder)"
            useDataCache="false"
            type="Rainbow.Storage.SerializationFileSystemDataStore, Rainbow"
            singleInstance="true"
          />

It should either prompt and or you should specify what the target framework is (be super cool if you could detect what the majority of all the other projects are using and set it to the same value?)

User story

As a developer, I want the Environment project to adhere to the habitat structure i.e.

/…
/[Module Name] // Module root folder, named after the module (without prefixes)
/code // Houses the main code for the module, for example the Visual Studio project with the module business logic or views.

Expected behavior

src\Project\Environment\code\Project.Environment.csproj

Actual behavior

src\Project\Environment\Project.Environment.csproj

Steps to reproduce the behavior

Create a clean project with Pentia tooling.

We need a way to have template files for a project inside the solution file structure.

So that you can customize the things you want to create inside a project.

Assembly should be Feature.[Name] & Default Namespace should be Feature.[name]
I guess you should also be possible to create Project or Foundation Modules, which should also be prefix correctly.

User story

when I adding a new project, the project get all target configurations

The template folder for the add generator is placed in the generators folder.
Should be placed under the add generator

@soen

User story

As a yo helix generator user, I want to run the generator with in VS package Manager console so that I can quickly spin a new helix solution without moving out of VS

Expected behavior

Generator provides a way to select the solution options with in VS

Actual behavior

VS hangs
https://sitecorechat.slack.com/files/phani_abburi/F49U0FGLT/-.powershell

Steps to reproduce the behavior

run yo helix in VS package manager console

As a Developer, I want to extend the default generator so that add my own generator steps. An example could be I want a step to add Sitecore.kernel refenreces

I would expected to find documentation on how to write such an extension

The documentation contains no description on how extend the generator

As a developer I've setup a new solution, and choosen to go with the option of using the pentia tools

after doing a npm install, i would be able to run gulp tasks.

But I get the following Error
The following error is shown within the visual studio output log
PATHTOPROJECT\node_modules.@pentia\publish-projects\build.js:14
this.AlwaysApplyName = this.solutionConfiguration.configurationTransform.AlwaysApplyName;
^
TypeError: Cannot read property 'AlwaysApplyName' of undefined
at new Build (PATHTOPROJECT\node_modules@pentia\publish-projects\build.js:14:75)
at Object. (PATHTOPROJECT\node_modules@pentia\publish-projects\build.js:64:16)
at Module._compile (module.js:397:26)
at Object.Module._extensions..js (module.js:404:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (PATHTOPROJECT\node_modules@pentia\publish-projects\gulpfile.js:9:13)
at Module._compile (module.js:397:26)

Steps to reproduce the behavior

To see this error

1. run yo helix
   Choose the option "with pentia tools"
   F

2. Point gulp to version 3.9.1 because i cant find a 3.9.5 version

3. do a npm install

4. Open visual studio and show output from Task runner.

External developer tells:

When I am adding a project to a solution through the helix generator, im met by this error

Error: C:\Users\xxx\AppData\Roaming\npm\node_modules\generator-helix\powershell\add-project.ps1 : File C:\Users\xxx\AppData\Roaming\npm\node_modules\generator-helix\powersh
ell\add-project.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?Li

Error: nkID=135170.
At line:1 char:1

I would expect to be notified about whether or not i have to run the generator in a special execution policy state. Im not, and the script execution fails.

We need to create a "getting started / how to use" so others can contribute to the tool.

Add a "Controller.cs" in the /Controllers folder and let it inherit from System.web.mvc.controller, and create a dummy ActionResult method, dummy poco view model, dummy factory and a dummy repository and let the repository get the view model in the controller and create a dummy view model and output some simple data in the view. So it is all hooked up nice and simple.

User story

As a developer, If I add serialization, I would also expect that the serialized files are also added, and the required NUGET packages are added to the the project

As a developper, I want to setup a new empty helix folution so that I can start working with sitecore using helix.

After running the generator i would expected to have a empyt vs solution

no solution file is created but correct folder structure is

Reproduce:
Run the generator choose empty helix solution

D:\Projects\Bane.Website [formsprojecthelixway]> npm install generator-helix -g
C:\Program Files\nodejs
`-- [email protected]

D:\Projects\Bane.Website [formsprojecthelixway]> yo helix:add Feature.Forms

 _-----_
|       |    ╭──────────────────────────╮
|--(o)--|    │    Lets generate that    │

---------´ │ project! │ ( _´U_ ) ╰──────────────────────────╯
/A\ /
| ~ |
'..'_
´ |° ´ Y

? Name of your project Feature.Forms
? Would you like to include Unicorn (serialization)? Yes
? Source code folder name src
? What layer do you want to add the project too? Feature layer?
? Choose target .net framework version? .net 4.6.1
Powershell - running: C:\Program Files\nodejs\node_modules\generator-helix\powershell\add-project.ps1 -SolutionFile 'D:\Projects\Bane.Website\Bane.Website.sln' -Name Feature.Feature.Forms -Type Feature -ProjectPath 'src\Feature\Feature.Forms\code' -SolutionFolderName Fea
ture.Forms
create src\Feature\Feature.Forms\code\Feature.Feature.Forms.csproj
create src\Feature\Feature.Forms\code\Properties\AssemblyInfo.cs
create src\Feature\Feature.Forms\code\App_Config\Include\Feature.Feature.Forms\serialization.config
create src\Feature\Feature.Forms\code\Properties\PublishProfiles\local.pubxml
Error: C:\Program : The term 'C:\Program' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Error: At line:1 char:1

• C:\Program Files\nodejs\node_modules\generator-helix\powershell\add-p ...

•   + CategoryInfo          : ObjectNotFound: (C:\Program:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  
  
  

Powershell - done running C:\Program Files\nodejs\node_modules\generator-helix\powershell\add-project.ps1-SolutionFile 'D:\Projects\Bane.Website\Bane.Website.sln' -Name Feature.Feature.Forms -Type Feature -ProjectPath 'src\Feature\Feature.Forms\code' -SolutionFolderName
Feature.Forms
D:\Projects\Bane.Website [formsprojecthelixway +1 ~0 -0 !]>

Remove files from solution (I would prefer this) or create the files.

User story

As a developer, I do not want redundant code so that I can survive.

Expected behavior

No unnecessary line of code

Actual behavior

This code doesn't do something useful

this.settings.ProjectName = this.settings.ProjectName;

Steps to reproduce the behavior

See: https://github.com/PentiaLabs/generator-helix/blob/master/generators/add/index.js#L45

User story

As a Developer, I want I want the build configuration to use AnyCPU so that so that the solution can build. (Please replace the <> areas and remove this parentheses)

Expected behavior

Solution builds using AnyCPU

Actual behavior

Solution does not build using Any CPU

Notice the added space.

Steps to reproduce the behavior

see http://yeoman.io/authoring/user-interactions.html

The powershell scripts can be rewritten into javascript, and should be to have as few dependcies on powershell as possible.

The powershell should be made into a module, if the functionality is needed as powershell else where.

Let field types have "{" and "}" in when creating the new ID.
i.e.
WRONG: public static readonly ID FieldId = new ID("d582b575-5fa5-463c-bcc7-e840fa83a995");
CORRECT: public static readonly ID FieldId = new ID("{d582b575-5fa5-463c-bcc7-e840fa83a995}");

Both way will compile and work. But in the real world and working with Sitecore - devs usually copy the ID of a item (including the "{" and "}" i.e. "{d582b575-5fa5-463c-bcc7-e840fa83a995}") and search the VS solution for the specific item ID. So if the T4 templates leave out the curly brackets the VS search hit is missed.

Note: per default the T4 template does create the ID of the template items with curly brackets - so it seems intentionel or simply an oversight to leave out the curly brackets when creating the data template ID's.

User story

When adding a project I get the Local.pubxml, but it is not included in the Project.Environment when creating a solution from scratch

Expected behavior

Local.pubxml is added, like when adding a project using yo helix:add

Actual behavior

Local.pubxml is not added

Steps to reproduce the behavior

create a new solution using yo helix, and select pentia tooling.

We should have a more clear license, without a license file and statement in the readme it's a bit hard.

Would recommend MIT or GPL.

First thing is to install Yo usng nopm.

Should probably be:

First thing is to install yo using npm.

A number of references that should be copy local true, are set to false, and the path is empty?

As a developer, I'm trying to add a project in an Empty Helix Solution.

Instead of generating the new project i'm getting an error message on the 'path must be a string':

events.js:161
throw er; // Unhandled 'error' event
^

TypeError: Path must be a string. Received undefined
at assertPath (path.js:7:11)
at Object.join (path.js:468:7)
at Object.Base.destinationPath (PATHTOGLOBAL\npm\node_modules\generator-helix\node_modules\yeoman-generator\lib\index.js:637:28)
at Object.writing (PATHTOGLOBAL\npm\node_modules\generator-helix\generators\add\index.js:148:62)
at Object. (PATHTOGLOBAL\npm\node_modules\generator-helix\node_modules\yeoman-generator\lib\index.js:408:23)
at PATHTOGLOBAL\npm\node_modules\generator-helix\node_modules\run-async\index.js:25:25
at PATHTOGLOBAL\npm\node_modules\generator-helix\node_modules\run-async\index.js:24:19
at PATHTOGLOBAL\npm\node_modules\generator-helix\node_modules\yeoman-generator\lib\index.js:409:9
at runCallback (timers.js:651:20)
at tryOnImmediate (timers.js:624:5)

Steps to reproduce the behavior

To see this error

1. run yo helix. Choose the option "Empty Helix Solution"

2. run yo helix:add

The index.js in feature, foundation and project are mostly copied.
They need to be refactored into a more DRY approach

Currently it is copied in, but as it is not part of the project file it does not show up in the project, and the LastUsedBuildConfiguration setting it therefore not modified if the build target is changed

As a developer I'd like to add custom questions to the Helix console when a developer is adding a new project or solution.

It would be nice to be able to call a library of predefined system methods, and in the long term extend with you own custom methods.

It could be json formatted configuration:

{
   "questions": [
   {
      "question": {
         "title": "Include files as part of visual studio?",
         "options": [ 
         {
	    "title": "Yes", 
            "action": "DoAttachAllFilesToVisualStudio()"
         },
         {
	    "title": "No", 
            "action": "NoAction()"
         }  
         ]
      }, 
      "question": {
         "title": "Some other question?",
         "options": [ 
         {
	    "title": "Yes", 
            "action": "DoSomeOtherQuestionMethodAlternativeYes()"
         },
         {
	    "title": "No", 
            "action": "DoSomeOtherQuestionMethodAlternativeNo()"
         }  
         ]
      }
  ]
}

User story

As a Developer, I want to have correct 'How To Add Project' documentation so that I can follow the documentation easily without confusion. (Please replace the <> areas and remove this parentheses)

Expected behavior

Documentation should say

yo helix:add

Actual behavior

Documentation says

yo helix:add [Projectname]

Steps to reproduce the behavior

RTFM :-D

User story

As a developer, I want to be prompted for an optional Module Group name when adding a module so that I can have groupings of logical modules together. This is documented as an optional file structure in section 2.3.1 of the Helix documentation.

Expected behavior

When adding a module to Helix, during the prompts, after Vendor Name prompt, I would expect to see an optional prompt for Module Group.

Actual behavior

The functionality does not prompt for Module Group.

Steps to reproduce the behavior

Adding a module does not provide you a method for specifying a module group.

User story

As a developer, I want to add a new project to my solution so that I can extend my solution.

Expected behavior

When the command yo helix:add is invoked on the solution root folder, I expect that I'm able to add a new project to the solution.

Actual behavior

When I run the command yo helix:add (with or without the optional [ProjectName] argument), I get the following exception:

module.js:471
    throw err;
    ^

Error: Cannot find module '../../modules/powershell'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\xxx\AppData\Roaming\npm\node_modules\generator-helix\generators\add\index.js:5:18)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)

Steps to reproduce the behavior

1. Install the latest version of the Helix generator (@1.0.10)
2. Create a new solution using the yo helix command
3. Try to add a new project to the solution using the yo helix:add command

On step 3, the error will appear.

It should be noted that this error is only present on version @1.0.10

see (http://helix.sitecore.net/principles/visual-studio/solutions.html)

User story

Helix documentation states that tests should be located under a tests sub folder for each module, see Helix Documentation, not in a solution folder.

Expected behavior

There should be no 4.Tests solution folder

Actual behavior

The is a 4.Tests solution folder

Steps to reproduce the behavior

yo helix

It should also be parsed to contain the correct information

As a developer, I want NuGet packages as part of my setup so that when I add a new project using the Helix generator the NuGet package is included.

User story

As a Developer I would like the option to add the T4 templates.