Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Template Management

Aperta
#359 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
typescript

Direzione di ricerca

Inizia esaminando il flusso della scheda Template-uri e il riferimento Figma collegato, quindi traccia il modo in cui i template vengono visualizzati, modificati, copiati, scaricati ed eliminati. Implementa i criteri di accettazione elencati, incluse le opzioni di menu basate sull’utilizzo, la denominazione delle copie, l’attribuzione al creatore, le azioni di download, la conferma e gli aggiornamenti dell’elenco; esamina inoltre la subtask sui dati di ONGHub.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement :rocket: web-app

User Story

As user, I want to manage contract templates for volunteers, so that I can ensure consistency in our organizational documents.

Description

The system should allow users to view, edit, duplicate and delete contract templates.

Actors

  • Web Users

Preconditions

  • User must be logged in and have navigated to the 'Template-uri' tab

Main Flow 1 (view template)

  1. User selects a template and clicks on the kebab menu.
  2. The system presents the following options: Vizualizeaza, Editeaza, Fa o copie, Descarca necompletat, and Elimina.
  3. User clicks on the Vizualizeaza option.
  4. The system displays the template in view mode.
  5. User has the option to download the template as a PDF.

Main Flow 2 (edit template)

  1. User selects a template and clicks on the kebab menu.
  2. The system presents the following options: Vizualizeaza, Editeaza, Fa o copie, Descarca necompletat, and Elimina.
  3. User clicks on the Editeaza option.
  4. The system displays the template in edit mode
  5. User updates the inputs according to preferences and clicks 'Save changes'.
  6. The system saves the updated template.

Alt. Flow 1 (duplicate template)

  1. User selects a template and clicks on the kebab menu.
  2. The system presents the following options: Vizualizeaza, Editeaza, Fa o copie, Descarca necompletat, and Elimina.
  3. User clicks on the Fa o copie option.
  4. The system creates a copy of the template and updates the list to include the new copy.
  5. The system displays a toast message confirming the successful operation.

Alt. Flow 2 (download template)

  1. User selects a template and clicks on the kebab menu.
  2. The system presents the following options: Vizualizeaza, Editeaza, Fa o copie, Descarca necompletat, and Elimina.
  3. User clicks on the Fa o copie option.
  4. The system creates a copy of the template and updates the list to include the new copy.
  5. A toast message is displayed confirming the successful operation.

Alt. Flow 3 (delete template)

  1. User selects a template and clicks on the kebab menu.
  2. The system presents the following options: Vizualizeaza, Editeaza, Fa o copie, Descarca necompletat, and Elimina.
  3. User clicks on the Elimina option.
  4. The system displays a confirmation modal.
  5. User confirms the deletion by clicking 'Sterge' button.
  6. The system deletes the template.

Business Rules

  1. The Editeaza and Elimina options must only be available for templates that have not been used to generate a contract.
  2. Both View mode and Edit mode must include an option for users to download the template.
  3. The delete option must trigger a confirmation modal to verify the user's action before proceeding.

Acceptance Criteria

  1. The system must display the following options for each template based on the number of uses:
  • For templates with 0 uses: Vizualizeaza, Editeaza, Fa o copie, Descarca necompletat, and Elimina.
  • For templates with more than 0 uses: Vizualizeaza, Fa o copie, Descarca necompletat.
  1. The option to download the template must be available in both View mode and Edit mode.
  2. Newly created templates using the copy function must be named by appending "_copy" to the original template's name.
  3. If multiple copies of the same template are created, subsequent copies will be named with incremental suffixes, such as "_copy(1)", "_copy(2)", and so on.
  4. For templates created via the copy function, the 'Creat de' value must reflect the name of the user who made the copy.
  5. Upon confirming the deletion by clicking 'Sterge' button, the system must delete the template and update the list accordingly.

Additional Information

  • Figma references: here

Subtasks:

  • Pull more data from ONGHub to make it available for template generation (organization cui, legal representative and his role)
Lingua principale
TypeScript
Stelle
3
Fork
2
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di code4romania/vic

Tutte le issue di code4romania/vic

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.