Decouple Importer from enforcing the use of placing default content in a module

Created on 8 March 2018, about 7 years ago
Updated 10 April 2023, almost 2 years ago

Problem/Motivation

The Importer service is coupled to only import from modules.
This is problematic because if we would like to build a user interface that imports from a uploaded .zip we cannot do that without creating a new Importer service (which would literally just be a huge code duplicate).

Proposed resolution

Change Importer::importContent to accept a path instead of a module, alternatively:
Add a new method allowing to import content from a given path.

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Needs review

Version

2.0

Component

Code

Created by

πŸ‡ΈπŸ‡ͺSweden johnwebdev

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024