mde/geddy — pull request #203 by MiguelMadero (2012-10-01 22:46:40+00:00)
Title: Updated Tutorial

There was a lot of yak shaving involved. I'm new with node, jake and the like so I had to do a lot of unrelated digging and fixed (or will log) a few bugs that I found along the way.

Please have a look and let me know what do you think, specially of the changes made to the templates, cli and other areas.

I also ended up with a long list of 'todos' that I'm not sure if I should log as issues or where would be the best place to discuss them. I'm pasting them here to start the discussion instead of just flooding the issue list.

Bugs:
- "host/controller/" doesn't work as "host/controller" when using routes
- Metrics isn't working (fails when starting geddy)
- Geddy (server) fails without warning if there's another server running on 4000. I think it should crash or at least show a warning and move to a different port (only in dev)
- If we have spaces when calling geddy jake fails because in cli.js we're calling cmds.split(' '). This is common when we have more than one property when calling scaffold, resource or model.
- If the generator fails midway, there's no indication of th error (I have an inprogress fix calling jake differently to listen the error event and WARN the user and ask them to use the -d flag for more details)
- It looks like if we change a rule in the model it affects the way we retrieve old date. For exmaple, I saved a TODO with a short title, then add a rule {min: 5} and the title of old TODOs is empty. There's no easy way to retrieve and compare using Geddy so that someone can fix the old, now invalid, TODOs.
- Why does the mongodb-wrapper has to be there as a LOCAL module. Could it be globally installed?
- If no default property is given Geddy will use id as the display property. I think we should pick the first property instead of id which is rarely useful. Ids should be internal and using it as a the default display property is misleading, I think Geddy should strive to use good defaults or force them to be explicit.

To re-test again with the HEAD
- Review this issue and update the documentation once it's fixed.
https://github.com/mde/geddy/issues/79
- The ajax PUT returns 302 to 'todos' and that returns 405
possibly others

I'm happy to follow this up. I just wanted to start wrapping the tutorial first and to start getting some input in some of the other things I found.