คำนำหน้า URL และ url_for ของ Blueprint

Often every route in a blueprint should sit under one path, like /admin. A url_prefix applies that path to the whole blueprint at once.

You pass the prefix when you register the blueprint. Every route inside then lives beneath that shared base path.

A route defined as /users under the prefix /admin becomes /admin/users. Flask simply joins the prefix and the route path.

Inside the blueprint, write routes without repeating the prefix. The prefix is set once at registration, so your view paths stay short.

Never type URLs as plain strings in templates. url_for builds the correct link from an endpoint name, so links survive path changes.

With blueprints, an endpoint is blueprint name plus view name. The users view in admin is the endpoint admin.users.

url_for already knows the prefix. Calling it for admin.users returns /admin/users, prefix included, with zero extra work.

Inside one blueprint you can use a leading dot as a shortcut. url_for(".users") means the users view in the current blueprint.

To link from blog to admin, name both parts fully. Always spell out the blueprint when crossing module boundaries.

Extra keyword arguments to url_for fill dynamic URL parts, so generated links stay correct even for parameterized routes.

Change a prefix later and every url_for link updates itself. This is why url_for beats hardcoded strings every single time. 🔗

How do you link to a view inside a blueprint?

A url_prefix mounts every blueprint route under one path, and url_for builds namespaced links like admin.users that update automatically. 🎉