Closed RayOffiah closed 6 months ago
I imagine this this related to this conversation https://asciidoctor.zulipchat.com/#narrow/stream/279644-users.2Fasciidoctorj/topic/Setting.20block.20context.20in.20AsciidoctorJ/near/406515443.
I have 2 comments:
At first glance, it's weird to move the methods to StructuralNode
because it is under ContentNode
. If we consider the property to be "writable", why not directly in ContentNode
?
It'd be great to better understand the use case if you could add a test with the use case you mentioned in Zulip? I do wonder if a new node could just be built some other way?
Thanks! Feel free to also open a PR against the v2.5.x branch if you want to have this in a minor release before 3.0.0 is released.
Yes, I can do that. Might have to wait until later in the week though.
Sent from Outlook for iOShttps://aka.ms/o0ukef
From: Robert Panzer @.> Sent: Saturday, December 16, 2023 5:39:40 PM To: asciidoctor/asciidoctorj @.> Cc: Ray Offiah @.>; Author @.> Subject: Re: [asciidoctor/asciidoctorj] Moved context functions to ContentNode (PR #1250)
Thanks!Feel free to also open a PR against the v2.5.x branch if you want to have this in a minor release before 3.0.0 is released.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: <asciidoc https://usb.report.cybergraph.mimecast.com/alert-details/?dep=Mq%2F4CVmt%2FNjj1FTVCTIisg%3D%3D118IcS3k%2B%2FwXUTPC%2BftIuBU3%2FFOwvE0iaFapGi4uQS2Z0Y50ndOvQnPzFs1NZeFOvUi4o3PEEvylz0Ywlz%2BTg%2B6QsKr4630bV5iBLUab0FyoWkYNuVPH8T3es6awfXbV2VAjVGhFDgh%2BPR6%2BU0CrEYskgE1DOzNaU4dpI99xFSG1R%2BYkMFtOIXtd%2F9AtgxxCTBNV5hyzzzoAs%2B4ZPoyvJEiWP0DmIVilkfpMB0zuJ3mInAYVqqdYHmMzXxA8Fa87q%2FHnrb9L2FnLzNxelHo3wxQNfAUlQSSLRGLPqtRefXaPNuCv0HKNlIKGO71p56o%2Bq3TapEcuiV9b6d%2FdMq%2Fp4jG6UhJgMsE0JQ31QcX%2BOP4wCvetZ%2FLN3ocoCVBECcmXknvA2Tebpxlc%2BamycnvOPo2MaIqzxXEy8Ru68%2BXEZ3%2FaCMCBVkZKSb%2F3nD9rhchqMxB38Pxe0wSX49WY1RNjDERoGqS4xbRMCQq7cEzlxv5fSjpy4yRcM3GNq8dAYQ0nL%2BzVrabRNnEY5ZdVV6LVtfbCF4slXb2o%2B0VWZTzJsxpiMGHwwWMzzY2rjOMtLKOYI5VisBGhGtBIxLxWMvgtA0zz1tOwmUvkuMSEb3iIrGUj8Kt1XSXpgIa1ZyhL6tLH2KyBfsAehMQLc1W6xTsvDd0igzttyPUrmHZhUfcUGl8UT0zboSRiRwujfPVI8Tdb%2BDiy49q8hgY%2FQqodlzLn%2FHtmQ3lZ9482Pv%2F6XloPHybbuJLFQwELorAwr7MFJqRYeatEx0PzhtTOxDXrsJDNb28EPq4B8JQhpc92THiqtqd6BAVpEMexC4i0X0bUU327neMMNY2GRLOyBAInvwu%2B7hdi%2BbVopUiYn6CRsHBxPDtDuSIqF5jkCHO4wl%2Fg2lO8JRhPJyW4rpnACUyKFXZDGiWCA9Uup3qJtPL2lDWts%2FCsxrAe11jq7pgqGExqSxb45zKcLEIGmNC2DpUK5oKaIbVFK1eedFSf5upJmJKSQJE%3D
Thanks! Feel free to also open a PR against the v2.5.x branch if you want to have this in a minor release before 3.0.0 is released.
— Reply to this email directly, view it on GitHubhttps://github.com/asciidoctor/asciidoctorj/pull/1250#issuecomment-1858879425, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASL3EZ4BBLLFRKZRCVECF6LYJXMFZAVCNFSM6AAAAABANYW7Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYHA3TSNBSGU. You are receiving this because you authored the thread.Message ID: @.***>
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.
Thank you for opening a pull request and contributing to AsciidoctorJ!
Please take a bit of time giving some details about your pull request:
Kind of change
Description
What is the goal of this pull request? Adding a function to set the Context of a node.
How does it achieve that? Added a setContext function to the ContentNode
Are there any alternative ways to implement this? Possibly.
Are there any implications of this pull request? Anything a user must know? Not that I know of.
Issue
If this PR fixes an open issue, please add a line of the form:
Fixes #Issue
Release notes
Please add a corresponding entry to the file CHANGELOG.adoc