URL路线功能的API设计中的代码复制与现实世界对象方法
我的API设计中的代码重复对象方法与URL路由功能:
# door_model.py
class Door:
def open(self): # "Door.open" written once...
...
# http_api.py (the HTTP server is separated from the real-world object models)
@app.route('/api/door/open') # ... written twice
def dooropen(): # ... written three times
d.open() # ... written four times!
d = Door()
如何避免在类似的API设计中避免这种不必要的名称重复?(同时保持现实世界对象之间的分离模型与HTTP服务器)。
使用对象模型(使用方法)和URL路由功能时,是否有一个通用模式可以避免名称的不必要重复? (几乎是模型视图控制器模式)
I have code duplication in my API design for the object methods vs. the URL routing functions:
# door_model.py
class Door:
def open(self): # "Door.open" written once...
...
# http_api.py (the HTTP server is separated from the real-world object models)
@app.route('/api/door/open') # ... written twice
def dooropen(): # ... written three times
d.open() # ... written four times!
d = Door()
How to avoid this unnecessary duplication of names in a similar API design? (while keeping a separation between real-world object models vs. HTTP server).
Is there a general pattern to avoid unnecessary duplication of names when using an object model (with methods), and URL routes functions? (nearly a Model View Controller pattern)
See also Associate methods of an object to API URL routes with Python Flask.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
如果我们为每个模型操作声明一条路由,并为每个模型执行相同的操作(在您的情况下,以有或没有参数为单位的相应方法),它将复制代码。通常,人们使用设计模式(主要用于大型项目)和算法来避免代码重复。我想显示一个简单的示例,该示例定义了一个通用路由并在一个处理程序功能中处理所有请求。
假设我们有以下文件结构。
门
的原型看起来像是我有条件地设置了C,
0
成功的出口代码,1
以备错误或失败。我们必须将模型动作分为一个共同的结构,将模型动作分为一个。
通过使用界面将组分开后,我们可以为每个界面实现一个通用处理程序。
通用
处理程序
实现,因此您可以使用不同的API路径和查询参数来控制模型的操作。
If we declare a route for every model action and do the same things for each (in your case, call the corresponding method with or without parameter), it will duplicate the code. Commonly, people use design patterns (primarily for big projects) and algorithms to avoid code duplications. And I want to show a simple example that defines one generic route and handles all requests in one handler function.
Suppose we have the following file structure.
The prototype of the
Door
looks likeWhere I conditionally set exit codes of the C,
0
for success and1
for error or failure.We must separate and group the model actions into one as they have a common structure.
After we separate our groups by usage interface, we can implement a generic handler for each.
Generic
handler
implementationSo you can control the actions of the models by using different API paths and query parameters.
您可以创建动态路线。您的情况的动态路线将是
api/door/< action>
。创建这样的路由以具有动态URL:
创建一个名为“操作”的类变量以使代码工作。例如,像这样的
action = ['open','Close']
You can create dynamic routes. A dynamic route for your case would be
api/door/<action>
.Create a route like this to have a dynamic url:
Create a class variable called actions to make the code work. For example like this
actions = ['open','close']
利用烧瓶蓝图模式,
您可以在
http_api.py.py
中在
api/door.py.py
或其他情况下使用,您可以使用:
You can leverage the flask blueprint pattern
In your
http_api.py
useIn Your
api/door.py
Or alternatively, you can use: