docs: B33 - Form extension #1664
Merged
Merged
Conversation
Extend the Form extension paradigm article (en+ru, line-synchronous). - Name what form extension contributes to a form declared elsewhere: further objects, the properties and actions shown for them, filters, and orders, plus refinement of already-declared elements; link to the owning Form_structure sections instead of restating them. - Add the positioning aspect: a contributed object, property, or action takes a position among the existing ones; for an object that fixes its place in the form's order of object groups, which governs a property's display group and the object group a filter applies to. - Fix the design cross-link to Form_design (the form-design abstraction) instead of Interactive_view, and keep EXTEND FORM about structure; the design is customized through the form-design mechanism. - Bring en/ru to parity in the Language section and align the heading with the sibling extension articles (Examples). Sources: LsfLogics.g formStatement/extendingFormDeclaration, sibling Class/Property/Action_extension articles, and EXTEND FORM usage in the platform system .lsf modules. Docs-only; no build/test run. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Extend the EXTEND FORM statement article (en+ru, line-synchronous). - Description: the blocks are written just as in a form declaration (link to FORM_statement#blocks), and inside them a developer may refer to the objects, properties, and actions already declared on the target form — to position a new element relative to an existing one or to filter an added object group by an existing object. - formName: a composite ID that must resolve to an already-existing form (this or another module); no new form is created, and (unlike FORM) no caption or icon is given. - Mark the block list optional in the syntax ([formBlock1 ... formBlockN]), matching the grammar (zero or more blocks). - Align the heading with the sibling statement articles (Examples) and keep en/ru line-synchronous (49 lines each). Sources: LsfLogics.g extendingFormDeclaration/formStatement and getFormForExtending/findForm in ScriptingLogicsModule; sibling EXTEND_CLASS_statement and FORM_statement articles. Docs-only; no build. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.