automatic workflow to request the correct item / address of a requester #144
No reviewers
j3d1
Labels
No labels
DevEnv Only
help wanted
question
Subsystem/Backend
Subsystem/Frontend
Subsystem/Mail
Kind
Breaking
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
c3lf/c3lf-system-3!144
Loading…
Reference in a new issue
No description provided.
Delete branch "clarity/ticket-requests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ich werde das nochmal rebasen - die commits aus 2025 sind quasi nicht mehr relevant für dieses feature.
9b84b4068c2efa8cd92ahinweis: accessibility checken
kommentar von jedi: pull request kleiner machen. es werden noch viele dinge angefasst, die man vielleicht nicht anfassen müsste.
e8156304d5c9f6e327dcc9f6e327dc62119ae2f4@ -42,1 +42,4 @@# Absolute base of the public site, used to build links that go out by mail.# Unlike PRIMARY_HOST and MAIL_DOMAIN above this is a full URL, not a bare host.PUBLIC_BASE_URL = os.getenv('PUBLIC_BASE_URL', f'https://{PRIMARY_HOST}')jedi: inline in die email, keine eigene variable
@ -0,0 +1,64 @@"""Response builders for stored files.jedi: komplette serving.py inlinen. das muss nicht in eine eigene datei ausgelagert werden.
@ -0,0 +1,80 @@"""The countries the application knows, keyed by ISO 3166-1 alpha-3.jedi: countries einfach vom user als string eingeben lassen.
@ -189,0 +318,4 @@ticket_updates.none_matched(self)class AddressRequest(TicketRequest):jedi: Zu komplex. Zu viele Methoden, warum transaction atomic?
@j3d1 die ganzen transaction.atomic sind jetzt raus.
und die alten methoden zur adress-validierung auch. die kamen noch aus dem shipment-feature; u.a. weil die adressen vor übergabe an den shipment-provider validiert werden mussten.
die open_for methode ist jetzt in .save() gewandert. Die Logik da drin bewirkt, das ggf. noch bestehende Requests gecancelt werden, wenn jemensch einen neuen Request erzeugt (z.b. mit einer neuen Item-Kombination o.ä.)
@j3d1 bevor du dir das frontend anschaust, würde ich das auch alles nochmal kleiner machen wollen. gebe dir einen headsup.
81ea997fc59d39adc291WIP: automatic workflow to request the correct item / address of a requesterto automatic workflow to request the correct item / address of a requesterwill be rewritten
f0316bd3378e9d1655deView command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.