Загрузка видео...

Не удалось загрузить видео

На главную

If you're looking for the easiest way to generate API docs for your Laravel application that are also beautiful, try this: 1. Composer require Scribe (knuckleswtf/scribe) This is an API doc generator that consumes your routes, requests, models, and resources, to auto-generate from 2. Configure Scribe Output Set the...

15,206 просмотров • 1 год назад •via X (Twitter)

Комментарии: 10

Фото профиля SecurityPal
SecurityPal2 лет назад

Questionnaire Concierge is now available as an API! With the new API, you can: 📝 Create new questionnaire request directly 🔍 Instantly search questionnaire details ⚒️ Build custom form and dashboard 🔗: #SecurityPal #SecurityQuestionnaires #API

Фото профиля James Brooks
James Brooks1 год назад

I gave a talk on Scribe! It’s such a great package 🥳

Фото профиля Sávio Resende
Sávio Resende1 год назад

I'm bookmarking this one, thanks man!

Фото профиля Steve Bauman
Steve Bauman1 год назад

Happy to help! It's a top tier package. Really grateful its open source and free

Фото профиля Pushpak Chhajed
Pushpak Chhajed1 год назад

uses scibe for api documentation. I will use sacler theme because its very minimalistic. Wasn’t aware about it thanks.

Фото профиля Steve Bauman
Steve Bauman1 год назад

Did not know about larasonic, very cool! Checking it out Also starred ⭐

Фото профиля Hugh Messenger
Hugh Messenger1 год назад

Scribe is freakin' awesome, so much easier than L5-swagger or any of the other alternatives.

Фото профиля Taf Hyseni
Taf Hyseni1 год назад

Used Scribe several times. Lately also found out Scramble which is similar to functionality and is beautiful as well:

Фото профиля Billiam
Billiam1 год назад

Sweet. We use GitBook but it’s a bit of a chore. Thanks for sharing

Фото профиля Steve Bauman
Steve Bauman1 год назад

I checked out GitBook as well and found you couldn't really customize much without paying for their cheapest plan at over $70 CAD per month! Wild

Похожие видео

I'm concerned we're entering a local maxima with CLIs, they're the wrong interface for agents The right interface is regular REST APIs with CIMD (same spec that MCP uses to allow for dynamic client registration) Your agent then writes code to interact with the API (like Cloudflare codemode) Think about how this works for humans today for the following action: "I want to set a DNS record on my domain" -> You Google "Vercel set DNS records" -> Docs page tells you what buttons to press -> You press buttons on a website, those call an API Now for agents, they search Google: -> "Set DNS record on Vercel Domain" -> they land on the same docs page, except it outlines what api endpoints are used as well -> the agent then calls those api endpoints for you, credentials are dynamically inserted where the agent can run them -> (optional) set auto approval policies / require approval of all non GET options by default You don't need separate interfaces for agents, nor do you really need separate skills for them CLIs have terrible discoverability, no input / output typing, they're harder to make profiles for for allowed / disallowed tools They work as a stop gap solution, but companies should be focusing on making good docs and APIs, not CLIs I've been prototyping this over at (open source if you want to play with what this world would look like - still early on it so appreciate feedback - open source and can run completely on your machine

Rhys

221,133 просмотров • 7 месяцев назад