Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add check to ensure BC breaking changes in rest descriptors are caught

Open
#6,219 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
tooling

Research direction

Start by reviewing the linked Batch library change in pull request 6208 and the existing Surface Breaking Change Detector. Compare the proposed rest-configuration artifact approach with a separate Configuration Breaking Change Detector, and define which descriptor changes must be detected for the work to be complete.

Written by the indexing model from the issue text.

Description

type: feature request

This change in the Batch library was not caught by our Breaking Change detector because it's a configuration change rather than a PHP surface change.

I see two solutions to this:

  1. Make the GAPIC generator create a surface artifact for rest configuration. Removal of these surface changes would be caught by the breaking change detector. This is similar to what we have in the Connection classes, where each method is implemented in a Connection/Rest class. The downside to this is it would create a LOT of overhead and also require a significant amount of work/changes in the generator, which would result in a lot of churn.
  1. Write a "Configuration Breaking Change Detector" that runs alongside the existing "Surface Breaking Change Detector". This could be expanded to check breaking changes in any descriptor config files.
Dominant language
PHP
Stars
1.2k
Forks
464
Avg merge
2d 2h
Merged PRs (30d)
103

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-cloud-php

All issues in googleapis/google-cloud-php

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.