improve error handling SchemaBuilder

[Genaker]

Extending error context :
Previousle:
Warning: Undefined array key "type" in /var/www/html/magento/vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php on line 91

Few Moments later:
Warning: Undefined array key "type" in /var/www/html/magento/vendor/magento/framework/Setup/Declaration/Schema/Db/SchemaBuilder.php on line 91 Error processing table catalog_eav_attribute column is_used_in_autocomplete

Help undersend the issue without heavy debugging!

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

1. ...
2. ...

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] improve error handling SchemaBuilder #39816: improve error handling SchemaBuilder

[m2-assistant]

Hi @Genaker. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[orkuncv]

For tables that are defined without columns and marked with disabled="true", like the example below:
<table name="amasty_stockstatus_quantityranges" resource="default" engine="innodb" comment="amasty_stockstatus_quantityranges" disabled="true"/>

You could consider adding the following check in your processing logic, e.g., around line 89:
if (!isset($tableColumns['column'])) { error_log("Missing 'column' key for table '{$keyTable}': " . json_encode($tableColumns)); continue; }

[Genaker]

For tables that are defined without columns and marked with disabled="true", like the example below:

<table name="amasty_stockstatus_quantityranges" resource="default" engine="innodb" comment="amasty_stockstatus_quantityranges" disabled="true"/>

You could consider adding the following check in your processing logic, e.g., around line 89:

`if (!isset($tableColumns['column'])) {

error_log("Missing 'column' key for table '{$keyTable}': " . json_encode($tableColumns));

continue;

}`

is it for me? Who should add?

[engcom-Hotel]

@magento create issue