Matthias MairWe are adding more #hotkeys to #inventree and I am unsure about how we can provide the best #ux - here is my current plan; happy for any #feedback
morgan@morgan that is not possible with the current frontend architecture; we moved away from frontend templating due to constant security / access control issues and poor boundaries between data access and presentation.
If you have a solution for that that does not involve JavaScript while having the same type checking support I would happily review. We did not find one 2.5 years ago when the current architecture was chosen but I am open to any new developments,
If you have a solution for that that does not involve JavaScript while having the same type checking support I would happily review. We did not find one 2.5 years ago when the current architecture was chosen but I am open to any new developments,
@matmair I'm a big proponent of just letting Django do it's job, but then I don't quite follow how a JS frontend helps with security, ACL, type checking, let alone a hulking react app. I spent days trying to get running using the bare metal instructions but the react app just refused to generate its CSS. I do a ton of Django work, and I would not call this a stellar dev experience.
@morgan re:complexity we have clear docs, independent ppl have packaged modern InvenTree for several platforms without any support from the core team. Yes it is a new thing to learn but so is any of the separation of concerns libs for Django.
And tbh I stopped caring about outsiders ideas about our devex seing how little actual maintenance anyone outside of the core team ever does. If someone spends time not for their own singular use case but overall quality and reliability I care.
And tbh I stopped caring about outsiders ideas about our devex seing how little actual maintenance anyone outside of the core team ever does. If someone spends time not for their own singular use case but overall quality and reliability I care.
@matmair the docs are not exactly clear, and appears to be missing steps. (Sorry, I cannot remember off hand what at the moment)
And NOTHING I tried could convince the frontend build to produce inventree.css.
I invoked, I pip'd, I npm'd, I examined all 10(!!!!) frontend config files but nothing would produce the expected CSS. I gave up eventually.
@matmair > If someone spends time not for their own singular use case but overall quality and reliability I care.
Fair, but I'd bet some talented django devs are turned away by the pain in the frontend.
I hope it gets to the point I can ignore the frontend enough to contribute to the backend and I'd encourage you to look at how NetBox handles this. Similar TS frontend, good form completions but I've never even had to look at it's frontend build process.
Also #webcomponents
@morgan I knew WC was coming. Everyone that has ever mentioned that to me has had a lot of great advice and no will to provide any concrete usage patterns that are not sizeable companies. Let alone any code.
Netbox is also similar: a sizeable company. We have 2 1/5 devs in their free time.
I have spend enough of my OSS time getting told how things should be done to know that this convo will waste more of my time than it will ever bring the project so I am done now.