Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] System configuration from modules #203

Merged
merged 1 commit into from
Oct 31, 2017

Conversation

oliverklee
Copy link
Contributor

This change is a prerequisite for switching the rest/api module to the
FOSRestBundle bundle.

@oliverklee oliverklee added this to the 4.0.0 ("phase 2") milestone Oct 16, 2017
@oliverklee oliverklee self-assigned this Oct 16, 2017
@oliverklee oliverklee force-pushed the feature/module-system-configuration branch from c8abaa0 to f4a8235 Compare October 16, 2017 16:29
@@ -137,6 +137,24 @@ the `extra` section of the module's `composer.json` like this:
}
````

You can also provide system configuration for your module:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example may be confusing because it relates to the core phpList 4 module, rather than an optional or third part module (even though they are technically managed in the same way). Maybe an example of a hypothetical third party module would be better to make it appear more immediately relevant? Or configuration of the optional REST API module.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@samtuke I've moved the section that explains that the key always needs to be phplist/phplist4-core. Does this help?

@oliverklee oliverklee force-pushed the feature/module-system-configuration branch 2 times, most recently from 1eb4e00 to 785e89b Compare October 17, 2017 11:33
@oliverklee
Copy link
Contributor Author

oliverklee commented Oct 18, 2017

After either this PR or #205 has been merged, I'll need update the rest-api and base-distribution packages before the other PR can be merged. Otherwise, we'll have at least the rest-api in a state where we would need to change two separate things in one PR (which I generally try to avoid) to get the build green again.

@oliverklee
Copy link
Contributor Author

This is blocked until the rest-api PR is merged.

@oliverklee oliverklee force-pushed the feature/module-system-configuration branch 2 times, most recently from a317b61 to 8337467 Compare October 31, 2017 17:08
This change is a prerequisite for switching the rest/api module to the
FOSRestBundle bundle.
@oliverklee oliverklee force-pushed the feature/module-system-configuration branch from 8337467 to ea177c0 Compare October 31, 2017 18:40
@phpList phpList deleted a comment from samtuke Oct 31, 2017
@oliverklee
Copy link
Contributor Author

The rest-api changes are merged. Merging this one.

@oliverklee oliverklee merged commit 9b8bca0 into master Oct 31, 2017
@oliverklee oliverklee deleted the feature/module-system-configuration branch October 31, 2017 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants