title: Can Flask have multiple blueprints on one view method?
body: <p>I am using Flask 1.x due to an OEM limitation.  Is it possible to stack blueprint routes for one view method and does order matter?</p>
  <p>I am trying to build an API and one of my thoughts was to try the following.  The <code>/main/event</code> rout (no id) will <code>GET</code> all current events for the logged in person; or, <code>POST</code> will handle a new event submission form.  The <code>/main/event/&lt;uuid:event_id&gt;</code> rout should <code>GET</code> the event with the id or <code>DELETE</code> the event based on id.</p>
  <p>Instead <code>POST</code> events complain about a missing <code>event_id</code> parameter.  Do I need to break the id and non-id actions into different view methods?</p>
  <pre><code>@main_blueprint.route('/main/event', methods=['GET', 'POST'])
  @main_blueprint.route('/main/event/&lt;uuid:event_id&gt;', methods=['GET', 'DELETE'])
  @login_required
  def event(event_id):
      ...
  </code></pre>
  <p><strong>Edit</strong></p>
  <p>I mentioned an incorrect version of Flask above (now corrected), I forgot which project I was working on.  I am tied to an OEM enforced version of Python and modules.</p>
  <p>I have been able to come close by adding <code>defaults=...</code> to the first route; basically faking a uuid4 if it is missing as in:</p>
  <pre><code>@main_blueprint.route('/main/event/', defaults={'event_id':'0'*32} methods=['GET', 'POST'])
  @main_blueprint.route('/main/event/&lt;uuid:event_id&gt;', methods=['GET', 'DELETE'])
  </code></pre>
  <p>This seems to &quot;work&quot; but is it necessary?</p>