improvements to FlaskResource

[asldevi]

add_url_rules takes the primary key name and its type and passes on to Flask
add as_view in FlaskResource, which is required for creating custom end points dynamically

[seocam]

Hey @asldevi! Could you please provide some tests in order to avoid regression?
Thanks!

[madsmtm]

Hi @asldevi, I love this feature, but I'd like to suggest something a little different. Maybe instead of specifying pk and pk_type in add_url_rules, I think we should specify instance_rule at the class level, so that it can be overwritten by a subclass with e.g.:

class MyResource(FlaskResource):
    instance_rule = r'<int:my_primary_key>/'
    def detail(self, my_primary_key):
        pass

Since the format of the parameters are tightly bound to the implementing class, and not to the Flask URL setup. Ideally, though, I'd like to be able to say:

class MyResource(XXXResource):
    def detail(self, my_primary_key: int):
        pass

And have that independent of the specific Resource implementation.

EDIT: Okay, I realise that this is an OLD issue, so if nobody has any complaints, I might go ahead and implement it myself? ;)

[Marcelo-Theodoro]

@madsmtm If you are avaiable, I think would be really nice!