From @saniyusuf on February 25, 2017 17:0

So I tried to run ionic g page myPageComponent it works just as it should.

However, I tried to run the same command this way ionic g Page myPageComponent and the CLI got very confused. The difference was that the P was uppercase. Can anyone please refer me to the place in the CLI where the params are gotten so I can just call a sanitization method that sanitizes params to lowercase to fix this?

Copied from original issue: ionic-team/ionic-cli#1946

Hi, I'm fairly new to Ionic and while I was trying the Ionic CLI I've noticed that the generator doesn't create the names of the files by following the Angular style guide.

See STYLE 02-01 and STYLE02-02.

For instance, if I do ionic g component box, this will generate several files named like this:

• box.html
• box.scss
• box.ts

Ideally, it should create something like this:

• box.component.html
• box.component.scss
• box.component.ts

The same pattern will follow when generating pipes, directives or services.

Maybe this behavior is something you deliberately chosed and I'm missing the point. If that's the case, please excuse my boldness. 😉

After generating a component/page/whatever, display some text telling the user what was created.

Thanks,
Dan

From @brandyscarney on October 18, 2016 15:30

From @richardshergold on October 18, 2016 13:34

If I do:

ionic g Page OrderDetails

I get an error saying that the available generators are:

Available generators:

• Component
• Directive
• Page
• Pipe
• Provider
• Tabs

what it wants is page in lower-case but in the list presented above, first letters are upper case

Copied from original issue: ionic-team/ionic-framework#8774

Copied from original issue: ionic-team/ionic-cli#1559

From @jgw96 on February 23, 2017 21:42

From @cfjedimaster on February 22, 2017 22:48

Ionic version: (check one with "x")
[ ] 1.x
[ x] 2.x

I'm submitting a ... (check one with "x")
[ x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/

Current behavior:
When I type ionic generate --list, I get:

Expected behavior:

I'd expect not to see "undefined" multiple times.

Steps to reproduce:

Run ionic generate --list

Related code:

insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):

Your system information:

 ordova CLI: 6.3.1
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.1.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.5.0
Xcode version: Not installed

By the way, notice "Cordova" is clipped off.

Copied from original issue: ionic-team/ionic-framework#10535

Copied from original issue: ionic-team/ionic-cli#1940

From @mburger81 on March 8, 2017 9:41

What version of the CLI are you using? Output of ionic --version

2.2.1

Short description of the problem:

I create a directive running ionic g directive draggable and see this in the created directive

/*
  Generated class for the Draggable directive.

  See https://angular.io/docs/ts/latest/api/core/index/DirectiveMetadata-class.html
  for more info on Angular 2 Directives.
*/

The link for the DirectiveMetadata is not the right one :)

What behavior are you expecting?

Perhapse this could be the right link?
https://angular.io/docs/ts/latest/guide/attribute-directives.html

Copied from original issue: ionic-team/ionic-cli#1961

If .editorconfig file is present upon using ionic generate, it should indent accordingly.

I think indent_style and indent_size is quite enough for starting out.

(suggestion) maybe with https://github.com/editorconfig/editorconfig-core-js for parsing the file

Add whatever you generate to the NgModule.

Thanks,
Dan

Let's say you want to run ionic generate page myPage (or my-page or MyPage, same issue)

You will find a new sub folder my with all my.* files

I would've expected something like my-page

Plus, the content is pretty strange to me
In my.ts

@Component({
    selector: 'page-my',
    templateUrl: 'my.html',
})

export class MyPage { ... }

page-myinstead of my-page, why is the selector reversed?
Class name is OK though.

From @faraazc on November 28, 2016 8:58

Short description of the problem:

ionic g page command is not registering the page component in app.module.ts file. Ideally it should include and register the component in the declarations array.
Angular-cli does registers components when scaffold.

What behavior are you expecting?

i would expect ionic cli to register page component in the declarations array of @NgModule decorator and also in entry points array if possible in the file app.module.ts

Steps to reproduce:

1. run below command
   ionic generate page page_name
   and check the behaviour in app.module.ts

Post the output of ionic info below please

Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.12
Ionic App Lib Version: 2.1.7
Ionic App Scripts Version: 0.0.45
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 7
Node Version: v7.1.0
Xcode version: Not installed

Copied from original issue: ionic-team/ionic-cli#1728

When generating tabs:
On the main tabs page the sub tabs pages are imported from the correct files, but in the component class names the "Page" suffix is missing - both in the input statement and on the assigned variables.

I hope I can fix it myself in the next couple of days. Please be patient and tell me, if I am doing something terribly wrong. It is hopefully going to be my first contribution to an open source project :)

From @jaufgang on March 9, 2017 19:33

When you create a component, page, service, etc with the cli generator, the filenames of the TypeScript files do not follow the naming conventions recommended in the official Angular Style Guide, in particular Style 02-02 and Style 02-03. The files are missing the conventional suffix for the file type.

This may not be a crucial or pressing issue, but for the sake of promoting best practices, I think it would be a good idea for the generator to conform to these standard conventions.

Copied from original issue: ionic-team/ionic-cli#1968