jupytercalpoly/jupyterlab-code-snippets

The Snippet preview (on the side) is too small

automataIA opened this issue · 6 comments

This is how look :
immagine

I can change this in the setting? How?

Hi Zawarud, at the moment the size of the snippet is not user-configurable. Could you tell me a little bit about why you want the preview to be bigger? Our initial through process when creating the preview was for it to just show a the general shape of the code, but we're always looking to improve things and your feedback would be helpful!

For see the code. In the case i have similar code snippet.
A question : Van I add this code in a cell line without create another One?

Got it, thank you for the feedback! At the moment the size of the preview will stay fixed and just provide a small preview of the basic outline of the code structure however there is an option to see the full snippet by clicking the 3 dots on the righthand side and selecting edit snippet.

In regards to your question, can you tell me a little bit more about what you mean by adding code without creating another one? Are you referring to creating another snippet or creating a new cell in the notebook or something else?

In regards to your question, can you tell me a little bit more about what you mean by adding code without creating another one? Are you referring to creating another snippet or creating a new cell in the notebook or something else?

Without creating another cell each time, but add the code in the selected line.

Got it, yes that is possible! After placing your cursor in an existing cell (where you want to paste), on the desired code snippet click on the three dots and select "Insert snippet" and the line of code will be inserted into the existing cell within a notebook without creating a new cell.

Screen Shot 2021-04-27 at 12 21 31 PM

Screen Shot 2021-04-27 at 12 22 07 PM

@zawarud
Hi, we just made the font size configurable in JupyterLab Advanced Settings. We will release the update next week once we fix the security vulnerability issue. Please refer to #201 for details.