- name: get orders
params:
- key: name
placeholder: 검색어
type: http
method: GET
# fetchFn: |
# const res = await fetch(
# `https://api.example.com/orders?q=${ name || "all" }`
# )
# const data = await res.json()
# if (data.status !== 200) throw new Error(data.error || "api error")
# return data.rows
fetchFn: |
const rows = [
{ id: 1, name: "Sample Order", price: 10000 },
{ id: 2, name: "Another Order", price: 15000 },
{ id: 3, name: "Hello World", price: 20000 }
]
const q = (name || "").trim().toLowerCase()
return !q ? rows : rows.filter(r => r.name.toLowerCase().includes(q))
1- name: get orders
2 params:
3 - key: name
4 placeholder: 검색어
5 type: http
6 method: GET
7 # fetchFn: |
8 # const res = await fetch(
9 # `https://api.example.com/orders?q=${ name || "all" }`
10 # )
11 # const data = await res.json()
12 # if (data.status !== 200) throw new Error(data.error || "api error")
13 # return data.rows
14
15 fetchFn: |
16 const rows = [
17 { id: 1, name: "Sample Order", price: 10000 },
18 { id: 2, name: "Another Order", price: 15000 },
19 { id: 3, name: "Hello World", price: 20000 }
20 ]
21 const q = (name || "").trim().toLowerCase()
22 return !q ? rows : rows.filter(r => r.name.toLowerCase().includes(q))
A simple way to build internal tools.
You're a backend developer. Your focus is on logic, data, and APIs—not CSS, not JavaScript frameworks, and not intricate UI components. But when you need an internal tool or a secure admin page, you're stuck building a frontend from scratch.
What if you could skip all that and get a functional, production-ready UI by simply defining a YAML file?
UI as code.
Define your page layout, tables, forms, and modals using a declarative YAML syntax. Select takes that file and automatically renders a practical, ready-to-use user interface. You get the UI you need without ever writing a line of frontend code.
Connect anything.
Your existing APIs are the source of truth. Select connects directly to your HTTP endpoints and consumes JSON data. There's no need for a separate database or a new backend—just map your JSON fields to the UI components you've defined.
Built for security, designed for speed.
From the start, Select is secure. It includes built-in features for authorization, role-based access control, and Google Authentication. And when it's time to make a change, you don't need a build process or a deployment pipeline. Just update your YAML file, and the UI changes instantly. It works with any tech stack that returns JSON, so you can focus on building what matters.
Turn your API into internal tool
When API meets YAML,
We render UI
Write YAML with API,
We render UI
When you don't need to develop frontend, there we are