dididy commented on code in PR #5075:
URL: https://github.com/apache/zeppelin/pull/5075#discussion_r2357447865


##########
zeppelin-web-angular/src/app/pages/workspace/notebook/paragraph/paragraph.component.html:
##########
@@ -40,26 +40,27 @@
       [colWidthOption]="colWidthOption"
       [pid]="paragraph.id"
       [isEntireNoteRunning]="isEntireNoteRunning"
-      [(enabled)]="paragraph.config.enabled"
-      [(tableHide)]="paragraph.config.tableHide"
-      [(colWidth)]="paragraph.config.colWidth"
-      [(title)]="paragraph.config.title"
-      [(fontSize)]="paragraph.config.fontSize"
-      [(lineNumbers)]="paragraph.config.lineNumbers"
-      [(editorHide)]="paragraph.config.editorHide"
-      [(runOnSelectionChange)]="paragraph.config.runOnSelectionChange"
-      (tableHideChange)="commitParagraph()"
+      [enabled]="paragraph.config.enabled"
+      [tableHide]="paragraph.config.tableHide"
+      [colWidth]="paragraph.config.colWidth"
+      [titleShow]="paragraph.config.title"
+      [fontSize]="paragraph.config.fontSize"
+      [showLineNumbers]="paragraph.config.lineNumbers"
+      [editorHide]="paragraph.config.editorHide"
+      [runOnSelectionChange]="paragraph.config.runOnSelectionChange"

Review Comment:
   > As far as I know, `title` is optional and is only used by 
`zeppelin-elastic-input`, while `config` is not optional. Could it be that 
we're looking at different parts of the code? (I checked `ParagraphItem` in 
`message-paragraph.interface.ts` and 
`notebook/paragraph/paragraph.component.ts`)
   
   I was actually referring to the internal properties of `paragraph.config`, 
more precisely to `ParagraphConfig`.  
   As for `paragraph.title`, as you mentioned, it’s treated as optional in 
`zeppelin-elastic-input`, so it should be fine to leave it as is without making 
any changes.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to