Pass arguments to the Blueprint constructor in the correct order

[owenniles]

According to the Flask API documentation, the Blueprint constructor expects to receive name as its first argument and import_name as its second argument.

It looks like there is a typo in the existing HireFire code, as __name__—a suitable value for import_name—is passed as the first argument, while the string "hirefire"—a suitable value for name—is passed as the second argument. In other words, the order in which the first two arguments are passed is reversed.

This part of the Flask API was unaffected by the upgrade from Flask 1.x.x to 2.x.x, but Flask 2.x.x will raise the following exception when it notices that the HireFire blueprint's name contains a dot (.):

In this PR, I switch the order of the first two arguments to the Blueprint constructor.

[codecov]

Codecov Report

Merging #62 (2c71876) into main (665217e) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage   55.55%   55.55%           
=======================================
  Files          11       11           
  Lines         423      423           
=======================================
  Hits          235      235           
  Misses        188      188           

Impacted Files	Coverage Δ
hirefire/contrib/flask/blueprint.py	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 665217e...2c71876. Read the comment docs.

[djsavvy]

Wow, great catch!

[ryanhiebert]

Cool, thank you!