Skip to content

Conversation

@larskemper
Copy link
Member

@larskemper larskemper commented Aug 11, 2025

resolves #11810

@larskemper larskemper self-assigned this Aug 11, 2025
@larskemper larskemper force-pushed the feature/migration-logging-required-fields branch from 23e60b2 to b256199 Compare August 11, 2025 09:42
@larskemper larskemper force-pushed the feature/migration-logging-required-fields branch from 4e9147e to b3ac25f Compare August 13, 2025 07:32
static::assertCount(20, $data);
static::assertSame('attr1', $data[0]['name']);
static::assertSame('text', $data[0]['type']);
static::assertCount(21, $data);
Copy link
Member Author

Choose a reason for hiding this comment

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

@MalteJanz I'm not quite sure why these changed/failed now with my changes and not earlier. Comparing them to sw55.sql, they seem fine, but I don't fully understand the details to be certain.

Copy link
Contributor

Choose a reason for hiding this comment

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

Strange, maybe this change in your MR caused this?

$fks[] = $foreignKey->getReferencingColumnNames();

On trunk it looks like this:

Copy link
Member Author

Choose a reason for hiding this comment

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

Good one, that's it. I changed it because getLocalColumns() was deprecated and replaced with getReferencingColumnNames(). For some reason, the previous method didn’t return the "first" column, so I think this behavior is correct now.

@larskemper larskemper force-pushed the feature/migration-logging-required-fields branch from e5673e1 to a3a33d9 Compare August 14, 2025 12:47
@larskemper larskemper force-pushed the feature/migration-logging-required-fields branch from a3a33d9 to e581615 Compare August 14, 2025 12:48
@larskemper larskemper force-pushed the feature/migration-logging-required-fields branch from 0a01359 to 1ebff3d Compare August 14, 2025 14:54
@larskemper larskemper marked this pull request as ready for review August 14, 2025 14:55
@larskemper larskemper requested a review from CR0YD August 18, 2025 07:36
@larskemper larskemper requested review from jozsefdamokos and removed request for DennisGarding August 18, 2025 11:10
@larskemper larskemper merged commit e0d0cd5 into feature/migration-logging-refactor Aug 18, 2025
7 checks passed
@larskemper larskemper deleted the feature/migration-logging-required-fields branch August 18, 2025 11:10
larskemper added a commit that referenced this pull request Aug 18, 2025
@larskemper larskemper requested a review from Copilot August 22, 2025 14:56
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR refactors migration logging to require profile name and gateway name fields instead of entity and source ID, consolidating logging messages and simplifying the logging structure. This change addresses issue #11810 by standardizing the required fields for migration logging.

Key Changes:

  • Refactored all logging classes to use profileName and gatewayName instead of entity and sourceId
  • Simplified log entry interface by removing detailed description/title methods and consolidating code patterns
  • Updated logging database schema and entity to match new required fields structure

Reviewed Changes

Copilot reviewed 118 out of 120 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
src/Migration/Logging/Log/*.php Updated all logging classes to use new constructor pattern with profile/gateway names
src/Migration/Logging/SwagMigrationLoggingDefinition.php Modified database schema to use new required fields
src/Migration/Logging/SwagMigrationLoggingEntity.php Updated entity properties to match new schema
src/Migration/MigrationContextInterface.php Changed connection getter to non-nullable
tests/ Updated test files to use new logging patterns and file existence checks

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants