abdfnx / resto Goto Github PK

So, I opened my Alacritty term with (800 x 600) and elements are not resizing.

Which makes it actually not usable.

it's an great idea to support resto file, but why ?

1. Send requests from files easily
2. Save time
3. a New Feature

so I choose yaml as the file format and the file name is .resto.yml

example

method: "POST"
url: "https://api.spacex.land/graphql"
contentType: "application/graphql"
openBodyEditor: true
# if `openBodyEditor` is false
body: |
   query {
     launchesPast(limit: 2) {
       mission_name
       launch_date_local
       launch_site {
         site_name_long
       }

       links {
         article_link
         video_link
       }

       rocket {
         rocket_name
         first_stage {
           cores {
             flight
             core {
               reuse_count
               status
             }
           }
         }

         second_stage {
           payloads {
             payload_type
             payload_mass_kg
             payload_mass_lbs
           }
         }
       }

       ships {
         name
         home_port
         image
       }
     }
   }
authType: "Bearer"
token: "MY_TOKEN"
# or basic auth
username: "USERNAME"
password: "P@$$w0rd"

that's it 👍

Hi, thanks for sharing a cool project with the world, and for maintaining a GitHub CLI extension.

Your repository abdfnx/gh-resto is an installable CLI extension and has the gh-extension repository topic, which helps it get discovered by gh extension search command. We use the topic to discover public extensions made by the community. All is good here!

However, this repository abdfnx/resto is not an installable CLI extension, and therefore should not have gh-extension topic. By removing the topic from this repo, you could help make gh extension search more efficient. Thank you!

Token storage change in latest release of gh

This is a message from the GitHub CLI team, maintainers of gh, writing to inform you that the most recent release of gh contains changes which may affect your extension. The latest release introduces the feature of storing authentication tokens in the system keyring (encrypted storage) instead of in a plain text file.
The keyrings that are supported are:

• Keychain on macOS

• GNOME Keyring on Linux (Secret Service dbus interface)

• Wincred on Windows

This has huge security benefits for the users of our tool and was one of our oldest outstanding issues. Unfortunately this change has the potential to break extensions that rely on utilizing the users authentication token to work.

In order to have continued compatibility with gh there are some actions you, as an extension author, need to take. These actions will depend on the implementation of your extension.

Extensions built in Go using go-gh:

1. Upgrade your go-gh version to v1.2.1, the latest version.

   • This can be done using go get github.com/cli/[email protected]

2. Verify that in your extension retrieval of the user authentication token is done using the auth.TokenForHost function.

   • If you were previously accessing the authentication token using any other method it will no longer work.
   • Automatic resolution of the authentication token when using the API clients will continue to work without changes.

All other extensions:

1. Verify that in your extension retrieval of the user authentication token is done by shelling out to the gh auth token command.

   • If you were previously accessing the authentication token using the gh config get command, reading the configuration file directly, or any other methods it will no longer work.

As of right now storing the authentication token in the system keyring is an opt-in feature, but in the near future it will be required and at that point if the changes above are not made then your extension will be broken for all users. If you have any questions/concerns about this change please feel free to open a discussion in the gh repo.

Thanks,
The GitHub CLI Team

something cool we should add it to resto, I think Install is a perfect idea

I am trying to make requests to my localhost but it gives me this error, how can I solve it.

Hi all, great job with that TUI! I'm looking for some more ease navigation with some keybindings like Ctrl + J(to go down to next field) and Ctrl + K(to go up to previous field) and something like that.
Also a F1 or ? keybind to show all keybindings. What do you think?

when I change an argument in resto, it's crashed

so we've to fix it

$ go install github.com/abdfnx/resto@latest
$ resto version
resto version

There's a new version of resto is avalaible:  → v0.1.6
To upgrade, run: go get -u github.com/abdfnx/resto

This can be avoided with

$ go install -ldflags "-X main.version=v0.1.6 -X main.buildDate="(date +%Y-%m-%d) github.com/abdfnx/resto@latest
$ resto version
resto version 0.1.6 2023-04-15

I’m not entirely sure what the right answer is given that you are using goreleaser to automatically apply the version number, but for those of us who prefer to go install… instead of brew install, it would be ideal to not have a spurious upgrade report with no real solution.