Jonatan Kłosko
Jonatan Kłosko
@mruoss honestly I think it's fine to skip it on CI. The tested code is rather encapsulated, so it should be evident when we want to run these tests. The...
@mruoss I did small adjustments to the form. I grouped the image picker and template under the same Pod section and moved storage to the bottom, since it's more of...
@mruoss thank you! I write the changelog when releasing, so no need to worry about that. Great that you enjoyed working on this and the timing was great, so no...
> I guess there is no way to set the "backend" attribute to "k8s", right? The smart cell itself should guess the default `"backend"` based on the environment. We could...
Hey @zhihuizhang17! Just to make sure we are on the same page. When developing locally you use a Teams workspace and have an S3 file storage that is accessible for...
One approach I can think of is allow a view where code cells are collapsed similarly to the Setup cell. So there is still a visual indicator of cell being...
@josevalim to clarify, the difference from setup cell would be that focusing the cell would keep the code collapsed, only entering insert mode would show the code. (I mean, we...
If we want to distinguish click I would make it more explicit, perhaps a pencil icon like the markdown cell, or some button in the collapsed placeholder, like "Collapsed cell...
Closing in favour of #2889.
The settings related to code editor are stored in browser local storage, rather than persisted to a file, like other Livebook settings (because Livebook can be hosted and used by...