Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
samizdat
samizdat
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Michał "rysiek" Woźniak
  • samizdatsamizdat
  • Issues
  • #70

Closed
Open
Created Sep 24, 2020 by Michał "rysiek" Woźniak@rysiek🔒Maintainer4 of 4 tasks completed4/4 tasks

Configurable plugin set and strategy

Since we already have a configuration system for the Service Worker (#69 (closed)), we can implement a way to configure:

  • what plugins are loaded
  • what is the content retrieval strategy (that is, what order are the plugins being deployed to fetch the content)
    • simple order (expressed as an array)
    • support for more complex structures with steps involving "any of these plugins" approaches (expressed as an array inside the simple ordered array, perhaps?)
Edited Sep 29, 2020 by Michał "rysiek" Woźniak
Assignee
Assign to
Beta
Milestone
Beta (Past due)
Assign milestone
Time tracking
None
Due date
None