is_url_for decorator. Fixes #77.

[jace]

No description provided.

[shreyas-satish]

Could this could use a more obvious name to indicate that it's calling flask's url_for? At first blush, it seemed like a recursive call.

[jace]

A comment above this line?

[shreyas-satish]

Hmm, as a reader I would find flask_url_for clearer than a comment, but this is perhaps a subjective detail.

[jace]

Agree, but our convention is to rename only when there's a conflict. We're not defining a url_for at the module level, and we don't want to cause conflict if some thing else in this module requires that function in future. A comment has less collateral impact.

[jace]

In hasjob.models.JobPost.url_for, the method does some additional processing. There's no scope for doing this in the decorator, so the model will still need the url_for method.