"ceedling new blah" fails when the current dir contains a project.yml file

[hmijail]

I think ceedling should fail more gracefully than just "rake aborted! Don't know how to build task 'new' (see --tasks)".

[mvandervoord]

Good point.

What kinds of things do you feel it should display? A list of commands acceptable commands? Should it attempt to guess what you meant?

[hmijail]

Not sure, I still know too little about the whole workflow with ceedling. For context, my use case was probably absurd (I did "ceedling new blah" inside of a dir created by a previous "ceedling new"), but this apparent nonsense error sent me chasing my tail for a while. (I had just upgraded the ceedling gem, so I feared that the "ceedling new" command had been somehow removed or botched)

I guess that the root problem here is that now ceedling delegates to rake too soon if project.yml exists, which probably isn't a good idea anyway: if the rakefile did actually contain a "new" target, suddenly ceedling would be acting in an unexpected way. Ceedling should rather filter its own commands before delegating to rake.

On 15 Apr 2016, at 16:49, Mark VanderVoord notifications@github.com wrote:

Good point.

What kinds of things do you feel it should display? A list of commands acceptable commands? Should it attempt to guess what you meant?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub #61 (comment)

[mvandervoord]

:) I see what happened for you. Thanks! I'll see what I can do to clean this up!

[mvandervoord]

Ceedling 0.20.3 fixes this by giving a polite error when the new, example, or examples commands are issued.