PRM_Software_AG/api-documentation
12
1
Fork 0
Code Issues 10 Pull Requests Activity

Strukturierung #11

New Issue
Open
opened 2024-06-19 10:30:15 +02:00 by Daniel_Hassert · 0 comments
Daniel_Hassert commented 2024-06-19 10:30:15 +02:00
Member
Copy Link

Ich schreib hier mal meine aktuelle Strukturierung nieder als Ergänzung zur aktuellen. Vielleicht hilfts ja was.

  • appointment
  • common
  • shared
  • shop
  • (auth)

Erklärung

Appointment

  • Alle Ressourcen betreffend Terminen und Terminplaner
    • Bsp.: Scheduler[...], AppointmentDuration, LastPossibileModificationMoment

Common

  • Ressourcen die eigentlich von jeder Anwendung benötigt werden
    • Bsp.: Exception, Exception, FooterModules, OnlineService, OnlineServiceDomain

Shared

  • Ressourcen die überall vorkommen können, aber nicht zwingend benötigt werden
    • Bsp.: CustomerStorage, CustomerStoragePosition, Articles, Branch, Customer, Employee

Shop

  • Ressourcen die nur den Shop betreffen?
  • Würde ich vermeiden, weil ich glaube das die Ressource die unter diesen Punkt fallen, auch in einen der anderen Bereiche fallen können.

Authentication

  • Ressourcen wie Session & OnlineUser.
  • aber bisschen zu wenig um eine eigene Untergliederung einzuführen?
    • dann besser in common aufgehoben
Ich schreib hier mal meine aktuelle Strukturierung nieder als Ergänzung zur aktuellen. Vielleicht hilfts ja was. - appointment - common - shared - ~~shop~~ - ~~(auth)~~ ## Erklärung ### Appointment - Alle Ressourcen betreffend Terminen und Terminplaner - Bsp.: `Scheduler[...]`, `AppointmentDuration`, `LastPossibileModificationMoment` ### Common - Ressourcen die eigentlich von jeder Anwendung benötigt werden - Bsp.: `Exception`, `Exception`, `FooterModules`, `OnlineService`, `OnlineServiceDomain` ### Shared - Ressourcen die überall vorkommen können, aber nicht zwingend benötigt werden - Bsp.: `CustomerStorage`, `CustomerStoragePosition`, `Articles`, `Branch`, `Customer`, `Employee` ### Shop - Ressourcen die nur den Shop betreffen? - Würde ich vermeiden, weil ich glaube das die Ressource die unter diesen Punkt fallen, auch in einen der anderen Bereiche fallen können. ### Authentication - Ressourcen wie `Session` & `OnlineUser`. - aber bisschen zu wenig um eine eigene Untergliederung einzuführen? - dann besser in `common` aufgehoben
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
Administrator Horst_Henschen Jeanette_Goldhahn Lirjeta_Sallahi Matthias_Rabbe Nico_Kroll Philipp_Bender Pierre_Christmann Rolf_Genee Yves_Hoeppe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: PRM_Software_AG/api-documentation#11
Delete Branch "%!s()"

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?