Project

General

Profile

Actions

Feature proposal #5209

closed

CBLib: Implement way for CB plugin libraries to specify DI alias

Feature proposal #5209: CBLib: Implement way for CB plugin libraries to specify DI alias

Added by krileon over 11 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Immediate
Assignee:
Target version:
-
Start date:
30 March 2015
Due date:
% Done:

100%

Estimated time:

Description

Currently there's no implementation for CB plugins to specify an API library DI alias (e.g. Application:Activity()).

Updated by krileon over 11 years ago Actions #1

  • Priority changed from High to Immediate

Updated by beat over 11 years ago Actions #2

  • Target version changed from CB 2.0.8 to CB 2.0.9

Updated by beat about 11 years ago Actions #3

  • Target version changed from CB 2.0.9 to CB 2.0.10

Updated by beat about 11 years ago Actions #4

  • Target version changed from CB 2.0.10 to CB 2.0.11

Updated by beat almost 11 years ago Actions #5

  • Target version changed from CB 2.0.11 to CB 2.0.12

Updated by beat almost 11 years ago Actions #6

  • Target version changed from CB 2.0.12 to CB 2.0.13

Updated by beat over 10 years ago Actions #7

  • Target version changed from CB 2.0.13 to CB 2.0.14

Updated by beat over 10 years ago Actions #8

  • Target version changed from CB 2.0.14 to CB 2.0.15

Updated by beat about 10 years ago Actions #9

  • Target version changed from CB 2.0.15 to CB 2.1

Updated by krileon over 9 years ago Actions #10

  • Target version changed from CB 2.1 to CB 2.2

Updated by krileon about 8 years ago Actions #11

  • Target version changed from CB 2.2 to CB 2.8

Updated by krileon almost 8 years ago Actions #12

  • Subject changed from Implement way for CB plugin libraries to specify DI alias to CBLib: Implement way for CB plugin libraries to specify DI alias

Updated by krileon almost 8 years ago Actions #13

This will require an improved plugin loading behavior as we would need to call createApplication followed by loading all the plugins, which can then prepare their DI as needed. This should be lightweight as all plugins should be using namespaced libraries minimizing what's actually loading. See #5703

Updated by beat over 3 years ago Actions #14

  • Target version changed from CB 2.8 to CB 2.8.1

Updated by beat almost 3 years ago Actions #15

  • Target version changed from CB 2.8.1 to CB 2.8.2

Updated by beat almost 3 years ago Actions #16

  • Target version changed from CB 2.8.2 to CB 2.9.0

Updated by beat almost 3 years ago Actions #17

  • Target version changed from CB 2.9.0 to CB 2.9.2

Updated by beat about 2 years ago Actions #18

  • Target version changed from CB 2.9.2 to CB 2.9.3

Updated by beat almost 2 years ago Actions #19

  • Target version changed from CB 2.9.3 to CB 2.10.0

Updated by beat over 1 year ago Actions #20

  • Target version changed from CB 2.10.0 to CB 2.11.0

Updated by beat 10 months ago Actions #21

  • Target version changed from CB 2.11.0 to CB 2.11.1

Updated by krileon about 2 months ago Actions #22

  • Status changed from Assigned to Rejected
  • Target version deleted (CB 2.11.1)
  • % Done changed from 0 to 100

No need for this as plugins become standalone Joomla extensions they'll just be using Joomla container API.

Actions

Also available in: PDF Atom