-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
apinotebookunder-discussionIssue is under discussion for relevance, priority, approachIssue is under discussion for relevance, priority, approach
Milestone
Description
On the API we don't make a strong (typed) difference between code cell and markdown cell - we only have the CellKind-hint. That makes some things a little cumber some, e.g
- Implementors of
executeAllCellneed to make sure they don't execute a markdown cell. Should we havenotebook#codeCellsornotebook#getCell(filter: CellKind)? - One can assign output to a markdown cell which I believe isn't wanted
- We always allow to change the language of a code cell to markdown, which at least for GH notebooks is unwanted
So, I wonder if notebooks should draw a more crisp line between code cells and markdown cells so that they are harder to confuse and more restricted in what you can do with them.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
apinotebookunder-discussionIssue is under discussion for relevance, priority, approachIssue is under discussion for relevance, priority, approach