Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pubsweet-frontend
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards

Heads up: This instance will undergo maintenance on Saturday at 12:00 CEST. The downtime is estimated to last 2 hours maximum

  • Richard Smith-Unna
  • pubsweet-frontend
  • Issues
  • #1

Closed
Open
Opened Sep 12, 2016 by Yannis Barlas@yannis

One fragment

Do you think it would be useful to have actions to get / update / delete one fragment by id?

The main use case I can think of is in the editor, where you only need the specific fragment to act on.
I am sure more use cases will come up.

This contradicts the current actions, which require the collection to be executed, but it seems a bit counter-intuitive to have to find the collection, in order to open / edit a specific fragment.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: blahah/pubsweet-frontend#1