diff options
| author | José Mota <josemota.net@gmail.com> | 2012-04-06 19:40:37 +0100 |
|---|---|---|
| committer | José Mota <josemota.net@gmail.com> | 2012-04-06 19:40:37 +0100 |
| commit | 3204575bfcd1f12db5945c8959073d40915cfdfe (patch) | |
| tree | 5b35a0896f91043c931482b5ecb99dc2aa154310 /_posts/2010-07-06-singular-resourcing-on-rails-3-beta.html | |
| parent | 6644e3213758ac5f8ea4f388d4dcf4105e7d4530 (diff) | |
Import all posts.
Diffstat (limited to '_posts/2010-07-06-singular-resourcing-on-rails-3-beta.html')
| -rw-r--r-- | _posts/2010-07-06-singular-resourcing-on-rails-3-beta.html | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/_posts/2010-07-06-singular-resourcing-on-rails-3-beta.html b/_posts/2010-07-06-singular-resourcing-on-rails-3-beta.html new file mode 100644 index 0000000..a06a9be --- /dev/null +++ b/_posts/2010-07-06-singular-resourcing-on-rails-3-beta.html @@ -0,0 +1,28 @@ +--- +layout: post +title: Singular resourcing on Rails 3 beta +tags: +- Development +status: publish +type: post +published: true +meta: + _edit_last: '1' +--- +Today I've been struggling on my project to be. I want to build it just right so I can learn Rails 3 the best way and enjoy the Ruby and Rails experience a little more. I love their ways, but sometimes it gets tough to go around the normal skeleton of an application.
+<h3>Singular resourcing was harder to grasp than I thought</h3>
+The idea is actually pretty simple to understand: for example, <em>you say you want a user to access only one resume</em> because that's the only one he would have. The scaffold generator adjusts the routing accordingly; well, at least it should.
+
+<!--more-->
+
+[gist id='464781']
+
+It should actually be <code>resume_path</code> in the singular but for the URL's to work you must have an <code>:as</code> parameter in the routes:
+
+[gist id='464784']
+
+I got frustrated for realizing I had to do extra effort to understand something that should have been linear. I need to work around on this. I was thinking of normal resourcing the posts so it could be searchable later on and everything. But it doesn't feel right, that's not the business model. A user has its own resume, period. If he is to look at another one, then a custom route will be made up.
+
+I'm asking for help now. If you have something to share regarding this matter, it would be absolutely great and I thank you very much.
+
+PS: Yes, the application started from this point. I have no users yet, no static content, no nothing. Perhaps starting an application with a singleton scaffold was a bad idea. Perhaps start with the users first? After all, they are the system and the resume should belong to them. |