Skip to content

Include abstract classes in the hierarchy with forwards on it - #498

Merged
evandongen merged 5 commits into
masterfrom
feature/fixedforwardpipe-forward-include
Jul 27, 2026
Merged

Include abstract classes in the hierarchy with forwards on it#498
evandongen merged 5 commits into
masterfrom
feature/fixedforwardpipe-forward-include

Conversation

@evandongen

Copy link
Copy Markdown
Contributor

Ok, not the clean up I wanted, but I think this is what we need. The forward is actually added in the Base64Pipe page, and in the hierarchy the FixedForwardPipe is now the parent.

I've built this, ran a frankframework build with attachFrankDoc and used that JSON to run the doc frontend to double check this. Looks pretty good up until now.

@evandongen
evandongen requested a review from Matthbo July 17, 2026 10:08
if(parent != null) {
elem -> elem.getAttributes(ElementChild.JSON_RELEVANT).isEmpty()
&& elem.getConfigChildren(ElementChild.JSON_RELEVANT).isEmpty()
&& elem.getForwards().isEmpty());

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is what did the trick

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What about parameters?
Will elements with inherited parameters now be skipped again?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I don't see how this relates to parameters?

@evandongen evandongen Jul 17, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

So much user specific files in the codebase, added some to the ignore files.

@evandongen evandongen linked an issue Jul 17, 2026 that may be closed by this pull request
@evandongen evandongen changed the title Feature/fixedforwardpipe forward include Include abstract classes in the hierarchy with forwards on it Jul 17, 2026

@Matthbo Matthbo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm missing some a test to prove that it works as intended

if(parent != null) {
elem -> elem.getAttributes(ElementChild.JSON_RELEVANT).isEmpty()
&& elem.getConfigChildren(ElementChild.JSON_RELEVANT).isEmpty()
&& elem.getForwards().isEmpty());

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What about parameters?
Will elements with inherited parameters now be skipped again?

Updated pnpm version and Node.js setup in workflow.
@evandongen

Copy link
Copy Markdown
Contributor Author

I'm missing some a test to prove that it works as intended

Fair enough, I'll add a test!

@evandongen
evandongen requested a review from Matthbo July 17, 2026 12:56
@evandongen
evandongen merged commit a58387c into master Jul 27, 2026
3 checks passed
@evandongen
evandongen deleted the feature/fixedforwardpipe-forward-include branch July 27, 2026 12:53
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.

Success forward defined in FixedForwardPipe does not work

3 participants