Uploaded image for project: 'Planet4'
  1. Planet4
  2. PLANET-4601

Fix issues in local development (to be broken into smaller tickets)

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Should have Should have
    • None
    • None
    • 4
    • Dev Tools
    • Sprint #132, Sprint #133

      Check if these bugs are still issues, create tickets for separate issues.

      There are some problems in localdev that can be time-consuming. I will start with the ones I already encountered, but feel free to add more items to this list or to split of items to a separate issue if they would be to big to take along here.

      Smaller fixes:

      • gutenberg plugins should be setup for development by default
      • class loadingĀ in planet4-plugin-medialibrary is broken because of incorrect autoloading. Classes are not found in localdev only, not a problem in other envs where composer install is ran with --optimize-autoloader, which preloads all classes. In localdev this doesn't happen automatically so a fresh setup fails without running `composer install --optimize-autoloader` in the plugin directory.

      Bigger fixes:

      • Make separate ticket: currently there is one big volume containing the entire wordpress directory. It would be better if there were separate volumes for the repositories that are developed. In that way we can easily reset the environment without losing data (uncommitted changes, git stashes, ...)
      • maybe move tests from base-fork to the repositories they apply to? That would make it easier to maintain them.

            pvincent Pieter Vincent
            pvincent Pieter Vincent
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: