ansaurus

Question

Keep track of reserved URLs (to enable vanity per-user URLs)

Answer 1

A:

Maybe you could make use of this?

But it looks like it raises on no match, so you might have to write a wrapper for it to rescue false on those cases.

I also just realized you would have to also inspect any match to make sure it's not the user route you will want it to match...

floyd 2010-01-24 22:34:31

Answer 2

+2 A:

Why not make things easier for yourself and simply do:

def validate
  reserved = %w(songs lyrics users posts)
  errors.add(:username, 'is not allowed') if reserved.include?(username)
end

John Topley 2010-01-25 08:05:15

So resign myself to manually updating this list when I add a new resource? Might be the least overall hassle here, I suppose

Horace Loeb 2010-01-25 19:35:10

I don't know your application, but realistically how often are you going to be adding new routes? Besides, the code above reveals its intent very clearly and is decoupled from the view. Finally, the Rails 3 router is a different animal, so any clever code you use to introspect the routes now is ripe for future breakage.

John Topley 2010-01-25 20:13:37

Answer 3

A:

Two counter-questions:

1) Why does the "favorites" page for each user need to live in the root of your URI tree?

2) How do you currently deal with the situation where two users choose the same username?

Peter 2010-01-25 12:14:13

Answer 4

A:

If you want to pull in a plugin to do this a useful one is friendlyid

From their site

FriendlyId is the “Swiss Army bulldozer” of slugging and permalink plugins for Ruby on Rails. It allows you to create pretty URLs and work with human-friendly strings as if they were numeric ids for ActiveRecord models.

More importantly for you it has support for making sure the urls generated don't match you controllers/paths

markdevilliers 2010-01-25 15:02:48

ansaurus

tags:

views:

answers:

Keep track of reserved URLs (to enable vanity per-user URLs)

related questions