Andreas Elia
Andreas Elia
> @andreaselia Hi, can you post a sample code with your solution? I will be really grateful Hopefully the code above is the right one for this.
> @andreaselia Yes, it's the right one, it's working, thank you Good to hear! You're welcome!
Hey @mikevandiepen, They look grouped correctly to me. Each route is under "equipment-accessories" correctly and them being within folders as per the end of the route name makes it easily...
Definitely understand, and it is indeed intentional so that at a glance you can see which route request is the "attach" one for example, or the "sync" one and so...
Sure thing, @mikevandiepen. You'll probably want to add a config option like `'flattened_routes' => false,` (default to false), and if it's true, then you'll want to avoid adding the last...
Going to close this to keep the repository manageable, but if you'd like to re-visit this in the future feel free to re-open it or let me know and I'd...
> Is this ready for review now? @mil3na a preliminary review would be great, please.
@mil3na I'll provide a video, but in terms of the error, the message itself is self explanatory, and a toast error isn't clear enough for this scenario, what would you...
> No, you should never throw an error like this at the user. You should handle it and show a more intuitive message. Either on the bottom left or a...
> What kind of validation are you missing? As it is a form, you can use the form validation: https://developers.raycast.com/api-reference/user-interface/form That form is provided by Raycast automatically via the preferences...