Validate all the services visibility (public/private)

Open on Drupal.org →

Created on 9 June 2014, almost 11 years ago

Updated 19 March 2025, 15 days ago

Problem/Motivation

Currently, all the services are defined as public.

Proposed resolution

As mentioned by @Crell on https://austin2014.drupal.org/session/road-81 presentation, we need to define APIs in service level. @fabpot pointed out the first obvious one on https://austin2014.drupal.org/session/dependency-injection presentation (Ref: https://www.youtube.com/watch?v=U6hq4qNT4_0#t=3380).

Remaining tasks

Walk through all the services and make sure they have correct visibility
Discuss
Issue patch
Test

User interface changes

N/A

API changes

Yes, as currently all services are public(and API), we might make few of them not-API?

Subtasks/Related tasks #

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

configuration system

Created by

🇬🇧United Kingdom vijaycs85 London, UK

Live updates comments and jobs are added and updated live.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Sign in to follow issues

Comments & Activities

Not all content is available!

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

Comment 15 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024