[24255] Consider external members as not plain

[MiguelCompany]

Description

This ensures that a type with an external member is never considered plain.

Depends on:

• [24255] Consider external members as not plain IDL-Parser#185

@Mergifyio backport 4.2.x 4.0.x 3.3.x

Contributor Checklist

• Commit messages follow the project guidelines.
• N/A: Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• N/A: New feature has been documented/Current behavior is correctly described in the documentation.
• Applicable backports have been included in the description.
  • We would need to update the backports, since they imply updating IDL parser to their corresponding backport.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[MiguelCompany]

@Mergifyio rebase

[mergify]

rebase

🛑 The pull request rule doesn't match anymore

Details

This action has been cancelled.

[MiguelCompany]

@Mergifyio backport 4.2.x 4.0.x 3.3.x

[mergify]

backport 4.2.x 4.0.x 3.3.x

❌ No backport have been created

Details

• Backport to branch 4.2.x failed

Git reported the following error:

Failed to merge submodule thirdparty/idl-parser (not checked out)
CONFLICT (submodule): Merge conflict in thirdparty/idl-parser
Recursive merging with submodules currently only supports trivial cases.
Please manually handle the merging of each conflicted submodule.
This can be accomplished with the following steps:
 - come back to superproject and run:

      git add thirdparty/idl-parser

   to record the above merge or update
 - resolve any other conflicts in the superproject
 - commit the resulting index in the superproject
error: could not apply 775c66b... Consider external members as not plain (#562)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

• Backport to branch 4.0.x failed

Git reported the following error:

Failed to merge submodule thirdparty/idl-parser (not checked out)
CONFLICT (submodule): Merge conflict in thirdparty/idl-parser
Recursive merging with submodules currently only supports trivial cases.
Please manually handle the merging of each conflicted submodule.
This can be accomplished with the following steps:
 - come back to superproject and run:

      git add thirdparty/idl-parser

   to record the above merge or update
 - resolve any other conflicts in the superproject
 - commit the resulting index in the superproject
error: could not apply 775c66b... Consider external members as not plain (#562)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

• Backport to branch 3.3.x failed

Git reported the following error:

Failed to merge submodule thirdparty/idl-parser (not checked out)
CONFLICT (submodule): Merge conflict in thirdparty/idl-parser
Recursive merging with submodules currently only supports trivial cases.
Please manually handle the merging of each conflicted submodule.
This can be accomplished with the following steps:
 - come back to superproject and run:

      git add thirdparty/idl-parser

   to record the above merge or update
 - resolve any other conflicts in the superproject
 - commit the resulting index in the superproject
error: could not apply 775c66b... Consider external members as not plain (#562)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".