Jiangge Zhang

@shonenada

Working in process

@shonenada How about the second way with a declarative usage? ``` python @nav.on(bar='top', item=nav.ItemReference('post_list')) @bp.route('/post//edit') def edit_post(post_id): post = Post.query.get_or_404(post_id) return render_template('edit_post.html', post=post) ``` The URL prefix way will restrict...

@shonenada I did a bad design in previous version. =。= The navigation items don't have own names. We can find a item by `nav.ItemReference` only, which has another optional argument...

@shonenada Just like this `@nav.on(bar='top', endpoint='post_list', args={'kind': 'latest'})`? I don't have better idea. :( Identifying item with the tuple of `endpoint` and `args` is really a bad idea. TAT

@LeonardBaranski Thank you for your contribution! Sorry for the late response since I put my time on a busy in-house project. I will have merged this after the revision.

可否介绍下这个的数据源呢…

I'm sorry for this delayed plan because of lacking mind for designing it : ( > so this project could focus on the Flask-specific parts This project don't have any...

I tried to use `mock` to check the final endpoint during requesting service API in [Flask-Qiniu](https://github.com/tonyseek/flask-qiniu/blob/master/tests/test_factory.py#L63-L71). Could we test the storage backends like it in this project too?

@lepture The document or official SDK of the service provider may rule the response format.