Please enable / Bitte aktiviere JavaScript!
Veuillez activer / Por favor activa el Javascript![ ? ]
Should we just teach yourself to break the app for bluprint? - bug-code.com Q&A

Should we just teach yourself to break the app for bluprint?

0 like 0 dislike
7 views
Should we just teach yourself to break the app for bluprint?
asked by | 7 views

2 Answers

0 like 0 dislike
If the application is rather big (relatively, more than 2-3 vyuha and 1-2 models) and could get complicated in the future, I think it is necessary to do at least 1 blueprint (e.g., core or common). Then, the complexity of the applications don't have to break bluprint the whole application, and it will be possible to make something from the first blueprint in individual. If the application is a little more complicated and will not be-the sense and in the same blueprint no.

In fact, bluprint in Flask-it is about dealing with complexity, because to reuse code in different projects in the Flask offered to do the extensions. Therefore, we need blueprint or not, and if needed, how much -- depends on how they simplify understanding of the application source code and navigate to the source code of the application.
answered by
0 like 0 dislike
In my case, after using blueprints I switched from Flask to Django, so I think if you see the need blueprints, the app has already grown and may be ask to rewrite in Django? Flask still micro framework for small applications and API
answered by
Welcome to Bug-code Q&A, where you can ask questions and receive answers from other members of the community.

24.8k questions

46.2k answers

0 comments

13.3k users

24,788 questions
46,220 answers
0 comments
13,321 users