Doonv

Results 70 comments of Doonv

I would like to implement a system that could read the scripts for some metadata (like a Description) and then put it inside the table. Any ideas on how metadata...

> > I would like to implement a system that could read the scripts for some metadata (like a Description) and then put it inside the table. Any ideas on...

Okay so this is what I came up with: ```py #?name: ~/.fehbg.nu #?version: 1.0 # #?short-desc: Selects a random image from a directory and sets it as a wallpaper #...

> Generally OK, but I suggest a few changes: > > 1. Don't store paths in name, make it just `fehbg` (or `fehbg.nu`) in this case > > 2. Add...

Alright so I got a test working of how getting the script metadata/manifests would work. ![image](https://user-images.githubusercontent.com/58695417/173052549-4652e51b-5dec-47a0-bf8d-a254891ecc33.png) I think its pretty good. Also the `get-script-data` function is very well documented. ![image](https://user-images.githubusercontent.com/58695417/173052899-2646ff04-da5d-4b11-accf-9527fc0080ea.png)...

> Excellent work! > > Though I still think that `#?name` should contain only the script's name and that file's location in nu_scripts repo should be included. Besides that, everything...

The auto-generation is working! ![image](https://user-images.githubusercontent.com/58695417/173136269-709d8ed5-d10a-4468-9655-6c7e70625c50.png) In this image the following properties are auto-generated: - `name`: The filename. - `script-url`: ` https://github.com/nushell/nu_scripts/blob/main/{PATH TO SCRIPT}` - `authors`: Fetched from the GitHub API....

Should we move this generator into it's own directory?

> When the template will be agreed on, we can... It's about time we start discussing the template and how it will look like, I'll start and we will make...

> > #?name: (Autogenerated) The name of the file > > Means the path to the file (for logical purposes)? No. That's a separate property which i forgot to mention...