Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D des
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • project
  • des
  • Issues
  • #405
Closed
Open
Issue created Mar 04, 2024 by Lena Kalleske@1772120097Developer

Update Entry per JSON-Objekt

Wie früher, sollte der Endpoint "/{projectId}/entry/update/{entryId}" auch JSON-Objekte annehmen können, also Content-Type = "application/json" akzeptieren.

siehe auch https://discourse.genealogy.net/t/datenbanksubstitution-per-post/821893

Edited Mar 04, 2024 by Lena Kalleske
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

Impressum | Datenschutz