Maybe I'm not grocking it, but how do I input validation when for POST requests
@api.route("/<string:subaccount>/user/<string:uniquename>") How do I do stricter validation of uniquename much like parsing payloads? Do I do it all manually in my routine? Or is there something more strict than <string:varname> ?
Ah what you are looking for is more of base flask functionality here. Flask provides a set of converters types to validate/typecast the route params. You can create your own converter types as mentioned here. https://uniwebsidad.com/libros/explore-flask/chapter-6/url-converters
If you don't want to define your own stuff and prefer a library doing it for you heres one https://github.com/Ge0rg3/flask-parameter-validation seems to support whitelists and regex validation
OAS3 allows for one response to have multiple schemas, through the use of oneOf, anyOf, allOf, not.
https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/
Does restx currently support this?
https://swagger.io/docs/specification/data-models/oneof-anyof-allof-not/
Does restx currently support this?
I currently have problems with marshalling my Responses.
I am trying to do the following:
test_model = Model(
"Test",
{
"_id": fields.String,
"name": fields.String,
"location": fields.String,
"ip": fields.String,
},
)
success_model = Model(
"Success",
{"data": fields.List(
fields.Nested(test_model)
)
},
)Without throwing any exception the data in the response is null
[{"status": "success", "data": null}']
Can somebody give me an advice?
It would be great to use @api.marshal_with(model) with multiple models, but not letting all of them be documented in swagger
FYI: i'm no longer a maintainer of python-restx. @ziirish is the final member left. I've removed my privs from Github. unfortunately, I have no time. and, honestly, i've started receiving personal emails asking about merges, etc. I don't have the capacity to deal with those.
1 reply
Honestly, at this point, flask-restx is so far behind so many projects in capabilities, even if we merged in a few things, it'd be worth users finding new frameworks
And I agree with you about the new frameworks that have more traction
I agree. Restx is quite limited
What i'm trying to do is to specify the structure of my Wildcard, i want it to be
input* instead of just *
This message was deleted
from flask import Flask
from flask_restx import Resource, Api, fields
api = Api()
app = Flask(__name__)
api.init_app(app)
input_model = api.model('Input', {
'type': fields.String,
'topic': fields.String,
})
output_model = api.model('Output', {
'type': fields.String,
'topic': fields.String,
})
@api.route('/input')
class Input(Resource):
@api.marshal_with(input_model, envelope='resource')
def get(self):
return {'hello': 'world'}
@api.route('/output')
class Output(Resource):
@api.marshal_with(output_model, envelope='resource')
def get(self):
return {'hello': 'world'}
control_model = api.model('Control', {
'name': fields.String,
'address': fields.String,
'inputs': fields.Wildcard(fields.Nested(input_model)),
'outputs': fields.Wildcard(fields.Nested(output_model)),
})
@api.route('/control')
class Control(Resource):
@api.marshal_with(control_model, envelope='resource')
def get(self):
return {'hello': 'world'}
if __name__ == '__main__':
app.run(debug=True)
This is the structure on swagger
I want instead of
* have input* and output*, to accept a object likecontrol = {
'name': 'Main Control',
'address': '100.100.100.100',
'input1':{},
'input2':{},
'output1':{},
'output3':{},
}