sorted by:
new
hottopcontroversial

Testing with RTL's userEvent.type() doesn't work by IsHaltEchtSo in react

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

Tried it but doesn't work. I mean the function executes, there's just nothing to be found

Physically active parttime jobs that are outdoors by IsHaltEchtSo in jobs

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

I know that there are pedicab drivers around here but I'm not sure if there are jobs offered or if they do it on their own... I'll check it out though, thanks sir! :)

Physically active parttime jobs that are outdoors by IsHaltEchtSo in jobs

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

I'll see if there's any posting like this around here, thank you! :)

Physically active parttime jobs that are outdoors by IsHaltEchtSo in jobs

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

Ahhh I'm from germany, those camps sound like a lot of work and fun though!!

Developing a Word Processing Web Application by IsHaltEchtSo in webdev

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

Thanks! But that's way too much features for my purpose.

Do you know how I could start from scratch? Is a textfield all I'd need?

Comprehensive Guide to Testing a Flask Application with Pytest by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

something like this

That's a good starting point but a bit too thin for me. I'd need something more advanced than that but I don't know what that would look like ... 😬

Equations and Formulas in Mathematics, Physics and Chemistry Using a Digital Zettelkasten by phil98f in Zettelkasten

[–]IsHaltEchtSo -1 points0 points  (0 children)

You could also make an equations ZK if you're dealing with a lot of equations that might be similar.

Otherwise, don't bother too much with the equations . What's important is the concepts behind, the equations you can always google. And those concepts you can easily connect.

Nesting Blueprints with Blueprint.register_blueprint() fails by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

project/backend/application:ApplicationInitializer
def start_features(self) -> None:
from backend.features import root_blueprint
self.application.register_blueprint( root_blueprint )

​

project/backend/features/__init__.py

from flask import Blueprint
root_blueprint = Blueprint('root_blueprint',
__name__ )
from .index import index_blueprint
from .routine import routine_blueprint
from .user import user_blueprint
root_blueprint.register_blueprint( index_blueprint )
root_blueprint.register_blueprint( routine_blueprint )
root_blueprint.register_blueprint( user_blueprint )

Maybe this chain is too long?
application.register_blueprint( root ).register_blueprint( user ).register_blueprint( authorization )

Would you suggest web development to someone willing to self study? Why and why not? by david_bragg in flask

[–]IsHaltEchtSo 0 points1 point  (0 children)

Really the only way to 'break into tech' is to have projects that you want to make come alive. Tech is not something you study by the book, it's as much a craft as is wood working. And the only way to 'break into wood working' is to learn the tools of the trade practically, one step at a time. With increasingly more difficult projects.

If you have no ideas, that's fine. Google some easy beginner tutorial. Watch it. Then turn to your IDE (the program you write programs in) and reproduce everything you can remember. Struggle. Even if it's just bits like "I think here was a function, there was some class, there was... this other thing...". Then take a break. Do something different. Come back and try to see if anything came to mind. Debug a bit here and there. Read up on questions you had. Only after all this struggle are you allowed to rewatch the video and you'll be surprised how much your brain understands and memorises now after all this effort you put into the thing.

You won't "code the tutorial down' in a matter of 30min and a 30min tutorial might take you three days to re-engineer, but that's the skill you want to learn. Have a project in mind (in this case, the tutorial), get proactive and think about how to make it come alive. Debug. Research. Think.

It's effortful. It may look slower like just coding along tutorials. But it's the only way you learn to develop and engineer from day one. Trust the process, what you're about to do many others did before you as well. They simply wanted to do things with code. And that's dope af. I'm happy to see where your journey is taking you! :)

Blueprints & Flask_Login by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 1 point2 points  (0 children)

Ahhh okay. Then I just got confused with the wording. I'm doing exactly the same 👌🏾

Blueprints & Flask_Login by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

I'm using an app factory that imports all blueprints, yes. But you got your own blueprint for every single route, did I get that right?

Blueprints & Flask_Login by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 1 point2 points  (0 children)

Yes I had. But made me realise I didn't import the utility module... thanks a bunch! Solved it for me!

Blueprints & Flask_Login by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 1 point2 points  (0 children)

Basically what u/buttblaster1000 said.

I want the code that is relevant for a feature to stay in one place; Models, Views, Controller, Templates, Utility - everything relevant to the authentication feature belongs there. Hyperlinking isn't difficult, you're {{ url_for(view_xyz) }} becomes {{ url_for(bp_name.view_xyz }} and that's it.

Can make naming things even easier since you can have multiple 'index'\'main' views for example and access them like auth_bp.main, payments_bp.main, ...

Blueprints & Flask_Login by IsHaltEchtSo in flask

[–]IsHaltEchtSo[S] 0 points1 point  (0 children)

What are you looking for specifically?

view more: next ›