Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frank!Doc: Apply Reintroduce annotation #3529

Merged
merged 5 commits into from
Aug 15, 2022
Merged

Frank!Doc: Apply Reintroduce annotation #3529

merged 5 commits into from
Aug 15, 2022

Conversation

mhdirkse
Copy link
Contributor

No description provided.

@mhdirkse
Copy link
Contributor Author

Draft because FRANKDOC.md remains to be updated.

@@ -34,27 +35,32 @@
@Category("Basic")
public class SenderPipe extends MessageSendingPipe {

@Override // to obtain proper order in FrankDoc and XSD
Copy link
Sponsor Member

Choose a reason for hiding this comment

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

Het is wel handig ergens in deze klasse een dergelijke tekst te zetten waarom deze methodes hier op deze manier in staan.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In my opinion, the @Reintroduce annotation should make this clear already. I have updated the JavaDoc comment of the Reintroduce class. If you hover over the @Reintroduce annotation, you see the explanation.

@mhdirkse mhdirkse marked this pull request as ready for review August 1, 2022 13:42
* child is repeated already without the need to add this annotation.
*
* Although it is technically possible to apply this annotation on attributes, doing so does
* not make sense because XML schema does not enforce the order in which attributes appear
Copy link
Contributor

Choose a reason for hiding this comment

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

Maar het heeft toch wel invloed op de volgorde waarin de attriubuten aan de FrankDeveloper gepresenteerd worden? Dat is relevant, c.q. maakt sense.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Dit stukje commentaar is nu weg.

Comment on lines 38 to 39
* This annotation has no impact on the Frank!Doc webapp. WeAreFrank! decided so because
* repeated config children would look confusing. If an overriding config child setter
Copy link
Contributor

Choose a reason for hiding this comment

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

ConfigChilderen moeten niet gerepeat worden, maar wel in de juiste volgorde staan. Daarom moet het ook invloed hebben op de Frank!Doc webapp. Zie mijn commentaar in de 'conversation' van dit PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Dit stukje commentaar is nu weg.

@gvanbrakel gvanbrakel merged commit 9b68a1d into frankframework:master Aug 15, 2022
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.

None yet

3 participants