Note:2: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
* Are the auxiliary files (e.g. composer.json, Gruntfile.js, package.json, CODE_OF_CONDUCT.md) that are getting added to extensions documented anywhere? Is there a way to generate them automatically? How are they kept up-to-date? Is there redundancy? | * Are the auxiliary files (e.g. composer.json, Gruntfile.js, package.json, CODE_OF_CONDUCT.md) that are getting added to extensions documented anywhere? Is there a way to generate them automatically? How are they kept up-to-date? Is there redundancy? | ||
* When an extension has a composer.json file, should it always be added to composer.local.json? | * When an extension has a composer.json file, should it always be added to composer.local.json? | ||
** Doing so for some of the "Semantic" extensions causes issues. | |||
** Doing some is required for some extensions. | |||
** What about other extensions? | |||
Revision as of 16:20, 2 September 2017
| Author | |
|---|---|
| Created | 2 September 2017 21:08:02 |
| Last Modified | 4 September 2017 16:30:44 |
| Tags | Extensions |
This note includes questions about the current state of installing extensions.
- Are the auxiliary files (e.g. composer.json, Gruntfile.js, package.json, CODE_OF_CONDUCT.md) that are getting added to extensions documented anywhere? Is there a way to generate them automatically? How are they kept up-to-date? Is there redundancy?
- When an extension has a composer.json file, should it always be added to composer.local.json?
- Doing so for some of the "Semantic" extensions causes issues.
- Doing some is required for some extensions.
- What about other extensions?