django-extensions
reagent
django-extensions | reagent | |
---|---|---|
12 | 41 | |
6,422 | 4,715 | |
0.3% | 0.1% | |
4.5 | 1.1 | |
7 days ago | 5 months ago | |
Python | Clojure | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-extensions
-
Ask HN: Anyone use a code to mindmap/flowchart tool?
django_extensions/utils/dia2django.py: https://github.com/django-extensions/django-extensions/blob/...
django_extensions/management/modelviz.py:
-
Color Django shell by development environment
I often perform operational tasks such as modifying data or debugging failures using the Django shell. In fact, anything I can't do through the admin or through management commands I use the shell for. The package django-extensions provides a shell on steroids that I much prefer over the built in shell. It allows you to run a custom REPL such as IPython or Ptpython and has autocomplete, command history, automatic model class imports and a myriad of other dev tools. shell_plus is for a Django programmer what a scalpel is for a surgeon.
-
How do I list all my endpoints across the whole project
It currently has a bug with the latest django update I think; so if it it isn't fixed by the time you try it, remember to check it out later, because django-extensions is genuinely useful.
-
Is it normal to forget a lot of commands despite having used them multiple times in the past?
alias m='exit_if_not_in_python_virtual_env && ./manage.py' alias mcs='exit_if_not_in_python_virtual_env && ./manage.py collectstatic' alias mcsu='exit_if_not_in_python_virtual_env && ./manage.py createsuperuser' alias mm='exit_if_not_in_python_virtual_env && ./manage.py migrate' alias mmm='exit_if_not_in_python_virtual_env && ./manage.py makemigrations' alias mrs='exit_if_not_in_python_virtual_env && ./manage.py runserver' alias ms='exit_if_not_in_python_virtual_env && ./manage.py shell' alias msa='exit_if_not_in_python_virtual_env && ./manage.py startapp' alias mt='exit_if_not_in_python_virtual_env && ./manage.py test' alias mts='exit_if_not_in_python_virtual_env && ./manage.py testserver' # [django-extension](https://github.com/django-extensions/django-extensions): alias msu="exit_if_not_in_python_virtual_env && ./manage.py show_urls" alias mvt="exit_if_not_in_python_virtual_env && ./manage.py validate_templates" alias msp="exit_if_not_in_python_virtual_env && ./manage.py shell_plus" alias mrsp="exit_if_not_in_python_virtual_env && ./manage.py runserver_plus"
-
Is there a way to enable sql tracing in Django?
I use https://github.com/django-extensions/django-extensions
-
How to get urls path from django views list ?
If you just want a list of all the available urls & paths in your app, take a look at the django-extensions package. It has a django management command show_urls, which will list them all out nicely.
-
django and the issue of doing too much under the hood
https://github.com/django-extensions/django-extensions has a command, show_urls which outputs the URLs rendered for a project along with the name of their view handler
-
Django for Startup Founders: A better software architecture for SaaS startups
# 1 million lines of logic and who knows how many queries
I've actually seen this pattern in every Django project :(
Regarding urls, instead of enforcing a flat file, I'd highly recommend always using django_extensions[0]. You'll get `shell_plus` that auto imports model and `show_urls` that you can grep for endpoint and gives you the handler.
[0] https://github.com/django-extensions/django-extensions
-
Failing the CI build if django migrations are out of date
A common mistake in django is to make a model change but forget to run makemigrations to generate a migration for the model change. Sometimes it is not entirely obvious when this need to happen. For example, let's say I'm using the django-extensions library and I define a model like:
-
Data Analysis with Django
Django Extensions has a shell_plus with notebook mode.
reagent
-
Ludic: New framework for Python with seamless Htmx support
Generating `HTML` from lisps has poisoned any other approach for me, see for example https://www.neilvandyke.org/racket/html-writing/, https://reagent-project.github.io/, and https://edicl.github.io/cl-who/
-
Produce HTML from S-Expressions
Hiccup syntax for Clojure uses hash maps (curly braces) for attrs, e.g. `{:style {:background "red" :margin "1em"}`
See Reagent which uses Hiccup synta: https://reagent-project.github.io/
(defn simple-component []
-
A History of Clojure (2020) [pdf]
* Single-Page App: shadow-cljs for the build concerns (https://github.com/thheller/shadow-cljs), Reagent with Re-frame for complex/large app (https://reagent-project.github.io and https://github.com/day8/re-frame). Even if we now prefer using HTMX (https://htmx.org) and server-side rendering (Hiccup way of manipulating HTML is just amazing, https://github.com/weavejester/hiccup).
- Leaving Clojure - Feedback for those that care
-
Clojure is a product design tool
The API documentation lists the most commonly and rarely used parts before going into detail and there are many usage examples.
Reagent has a nice intro tutorial (classic todo-app): http://reagent-project.github.io and many other helpful tutorials and resources for beginners: https://cljdoc.org/d/reagent/reagent/1.2.0/doc/documentation...
However, since Reagent is still stuck with class-components for more complex behavior and relies on Hiccup, which is nice but has a performance cost compared to pure React, I am unsure about its future. Like some others in the Clojure community, I have moved to thin React wrappers like Helix and use Refx to integrate those with re-frame. It may be a bit confusing right now for beginners since there is no “golden path”.
Also, unfortunately, many smaller libraries are poorly documented and it seems like it is expected from the developer to dig into the source code to find out what’s going on.
What I found the most difficult as a beginner was how to setup a project in ClojureScript in the first place, like all the configuration in shadow-cljs, how it interacts with deps.edn, how it integrates with npm, the REPL, etc. But dev/build config has always been a weak spot for me, so it might be just that.
Overall, I still very much enjoy working with Clojure(Script), more than in any other language. Anyone who likes Lisps and functional programming should give it a try (and be sure to watch Rich Hickeys amazing talks!).
-
Ask HN: How can a BE/infra developer handle the FE side of personal projects?
have you tried cljs and reagent? it’s a different vibe.
my bootstrap: https://github.com/nathants/aws-gocljs
the project: https://reagent-project.github.io/
- What are the enduring innovations of Lisp? (2022)
-
Building a website like it's 1999... in 2022
Clojure people have been doing this for a decade or so. It’s really so much better to work with. All started with Hiccup and when React came along you got Reagent and many more developments building on the idea.
-
React.dev
> But Reagent supports functional components as well, with hooks and all.
I addressed this already: while reagent is able to emit function components, there is a performance penalty to this.[1]
> I also very much like Hiccup, and so do many of us, because code is data and data is code, and Helix has decided not to support that.
Hiccup is convenient to write, but it is a constant run-time cost and a significant storage cost given that you have to store long series of constructors to cljs.core.PersistentVector in your bundle, have the JS runtime actually construct the vector, then pass it through a Hiccup interpreter to finally produce DOM nodes and throw away the persistent vector, only to repeat this entire process again on re-render.[2]
> Helix has decided not to support that.
That is simply not true. From the Helix documentation[2],
> If you want to use libraries like sablono, hicada or even hx hiccup parser, you can easily add that by creating a custom macro.
These are all Hiccup interpreters you can readily use.
IME there is very little difference between using the $ macro in Helix and writing Hiccup. I do not really miss Hiccup when I use Helix, and you still have data as code ;)
While this is from an unrelated project, there are benchmarks[3] done against Reagent that demonstrate the sheer overhead it has. In practice it is not a big problem if you rarely trigger a re-render, but otherwise it is a non-trivial cost, and if you want to use modern React features (like Suspense), there is a lot of r/as-element mingling going on, converting cases, etc. that simply make Reagent feel more tedious to use than Helix.
Also, the newer UIx2, which largely borrows from Helix, is "3.2x faster than Reagent" according to one of the contributors.[4]
I think it'd be worthwhile to benchmark all of these libraries against each other and record the data in one place. Maybe I'll get around to doing it this weekend :)
---
[1] https://github.com/reagent-project/reagent/blob/master/doc/R...
[2] https://github.com/lilactown/helix/blob/master/docs/faq.md#w...
[3] https://github.com/roman01la/uix#benchmarks
[4] https://github.com/pitch-io/uix/pull/12
-
React is a fractal of bad design
Reagent is peak React. All the good stuff without any of the hook and readability problems the article describes.
No affiliation, happy user for years.
https://github.com/reagent-project/reagent
What are some alternatives?
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
helix - A simple, easy to use library for React development in ClojureScript.
re-frame - A ClojureScript framework for building user interfaces, leveraging React
django-crispy-forms - The best way to have DRY Django forms. The app provides a tag and filter that lets you quickly render forms in a div format while providing an enormous amount of capability to configure and control the rendered HTML.
shadow-cljs - ClojureScript compilation made easy
django-seed - :seedling: Seed your Django database with fake data
fulcro-rad-demo - A demo for Fulcro RAD using either SQL or Datomic databases.
django-sql-dashboard - Django app for building dashboards using raw SQL queries
storybook.js-with-shadow-cljs
Django - The Web framework for perfectionists with deadlines.
hyperscript - Create HyperText with JavaScript.