Korxona ilovalari interfeysi
Omborchi 12 000 ta mahsulot ichidan “UN-” bilan boshlanadigan va qoldig‘i kam bo‘lganlarini qanday topadi?
Excel dagidek barcha qatorni bitta sahifaga chiqarib qo‘ysak-chi? Avval taxmin qiling.
Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
when(), oq ro‘yxatli saralash va paginate()->withQueryString() bilan xavfsiz ro‘yxat so‘rovinipaginate, simplePaginate va cursorPaginate dan vaziyatga mosiniold(), @error va Livewire validatsiyasini hujjat formalarida#[Url], WithPagination va wire:model.live.debounce bilanServer tomonida render va SPA
Server render (SSR) va bir sahifali ilova (SPA)
Server tomonida render (Blade, Livewire)
- HTML serverda yasaladi, brauzer tayyor sahifani oladi
- Bitta kod bazasi, bitta til — PHP
- Sessiya va
@canbilan ruxsatlar (5-mavzu) - Validatsiya bir joyda — FormRequest
- Kamchilik: klassik Blade da har harakat — to‘liq qayta yuklash
Bir sahifali ilova (Vue, React)
- Brauzer JSON oladi va sahifani o‘zi chizadi
- Juda yuqori interaktivlik, offline rejim mumkin
- Mobil ilova bilan umumiy API
- Narxi: frontend + API, ikki joyda validatsiya
- Token autentifikatsiya, build jarayoni, JS mutaxassis
To‘rt yondashuv: qanday ishlaydi va qachon mos
| Yondashuv | Qanday ishlaydi | Qachon mos |
|---|---|---|
| Blade (klassik SSR) | Controller → Blade → HTML; har harakat — yangi sahifa | Oddiy CRUD, hisobotlar, ichki portallar |
| Blade + Livewire 3 | Komponent holati serverda; AJAX bilan faqat o‘zgargan HTML | Jadval, filtr, dinamik formalar — PHP jamoa |
| Inertia.js + Vue/React | Laravel controller sahifaga props beradi; API shart emas | Boy UI kerak, lekin bitta Laravel ilova |
| SPA + REST API | Alohida JS ilova, server faqat JSON qaytaradi | Mobil/offline, bir nechta klient, katta frontend jamoa |
Bitta Livewire so‘rovining aylanishi
Birinchi render
Harakat
wire:model.live.debounce.300ms="search"AJAX so‘rov
POST /livewire/update ga snapshot va o‘zgarishlarni yuboradiServerda
$search yangilanadi, updatedSearch() hook, render()DOM yangilanishi
debounce, wire:model.blur va kerakli joyda .live muhim.1-bo‘lim yakuni: Server tomonida render va SPA
Ma’lumotlarga boy ekranlar
Ro‘yxat ekrani nimalardan iborat
Mahsulotlar, buyurtmalar, hisob-fakturalar — barcha ro‘yxat ekranlari bir xil tuzilishda bo‘lsa, foydalanuvchi tez o‘rganadi.
1Sarlavha va asosiy amal
products.manage ruxsati borlarga)2Filtrlar paneli
3Jadval
4Sahifalash
5Bo‘sh holat
6Yuklanish holati
wire:loading — “Qidirilmoqda…”, jadval xiralashadiMahsulotlar jadvali: bo‘sh holat bilan
<table class="table table-sm table-hover"> <thead class="sticky-top"> <tr><th>SKU</th><th>Nomi</th><th>Kategoriya</th> <th class="text-end">Narx, so‘m</th></tr> </thead> <tbody> @forelse ($products as $p) <tr> <td><code>{{ $p->sku }}</code></td> <td>{{ $p->name }}</td> <td>{{ $p->category->name }}</td> <td class="text-end">{{ som($p->price) }}</td> </tr> @empty <tr><td colspan="4">Hech narsa topilmadi</td></tr> @endforelse </tbody> </table>
SKU Nomi Kategoriya Narx, so‘m UN-001 Un oliy nav 50 kg Un mahsulotlari 385 000 GR-007 Guruch lazer 25 kg Yorma 41 000
htmlspecialchars bilan ekranlanadi — XSS dan himoyawith('category') bo‘lmasa — N+1Pul va qoldiq belgisi — sof PHP
function som(int $x): string { return number_format($x, 0, '.', ' ') . ' so‘m'; } function badge(int $qty, int $res, int $min): string { $free = $qty - $res; return match (true) { $free <= 0 => 'tugagan', $free < $min => 'kam', default => 'yetarli', }; } echo som(1250000), "\n"; echo badge(120, 20, 50), ' | ', badge(30, 0, 50), "\n"; echo badge(5, 5, 10), ' | ', som(-45000);
1 250 000 so‘m yetarli | kam tugagan | -45 000 so‘m
stocks)<span class="badge">{{ badge(...) }}</span> — rang + matn2-bo‘lim yakuni: Ma’lumotlarga boy ekranlar
1-topshiriq: Qoldiq belgisi (badge)
Mahsulotlar jadvalida har bir qator yonida qoldiq holati ko‘rsatiladi. Mavjud qoldiq = quantity − reserved. Mavjud qoldiq 0 bo‘lsa — tugagan, minStock dan kichik bo‘lsa — kam, aks holda — yetarli. Agar quantity yoki reserved manfiy bo‘lsa yoki reserved > quantity bo‘lsa, bu invariant buzilganini bildiradi — DomainException tashlang.
Imzo: function qoldiq_badge(int $quantity, int $reserved, int $minStock): string
Qaytaradi: Satr: 'tugagan', 'kam' yoki 'yetarli'.
qoldiq_badge(120, 20, 50)
"yetarli"
Filtrlash va saralash
ProductController@index: filtr, saralash, sahifa
public function index(Request $request): View { $search = trim((string) $request->query('search')); $sort = in_array($request->query('sort'), self::SORTS, true) ? $request->query('sort') : 'name'; $dir = $request->query('dir') === 'desc' ? 'desc' : 'asc'; $products = Product::query() ->with('category:id,name') ->when($search !== '', fn ($q) => $q->where( fn ($w) => $w->where('name', 'ilike', "%{$search}%") ->orWhere('sku', 'ilike', "%{$search}%"))) ->when($request->integer('category_id'), fn ($q, $id) => $q->where('category_id', $id)) ->orderBy($sort, $dir)->orderBy('id') ->paginate(20) ->withQueryString(); return view('products.index', compact('products')); }
GET /products?search=un&category_id=3&sort=price&dir=desc SQL (soddalashtirilgan): select * from products where (name ilike ? or sku ilike ?) and category_id = ? and deleted_at is null order by price desc, id asc limit 20 offset 0 bindings: ['%un%', '%un%', 3]
['sku', 'name', 'price', 'created_at'] — oq ro‘yxatSaralash parametrini xavfsiz tahlil qilish
const SORTABLE = ['sku', 'name', 'price', 'created_at']; function parseSort(?string $p): array { $p = $p ?: 'name'; $dir = str_starts_with($p, '-') ? 'desc' : 'asc'; $col = ltrim($p, '-'); if (!in_array($col, SORTABLE, true)) { return ['name', 'asc']; // ruxsat etilmagan → standart } return [$col, $dir]; } foreach (['-price', 'sku', null, 'password; DROP'] as $p) { echo implode(' ', parseSort($p)), "\n"; }
price desc sku asc name asc name asc
- — kamayish tartibiFoydalanuvchi ustun nomini tanlamasin
Noto‘g‘ri: kirish to‘g‘ridan-to‘g‘ri SQL ga
->orderBy($request->sort)— istalgan ustun nomi?sort=password— maxfiy ustun bo‘yicha saralash->orderByRaw($request->sort)— SQL injection- Noma’lum ustun — 500 xato va stack trace
To‘g‘ri: oq ro‘yxat va standart qiymat
SORTS = ['sku', 'name', 'price']- Yo‘nalish faqat
ascyokidesc - Noma’lum qiymat → standart saralash
->orderBy('id')— barqaror tartib
3-bo‘lim yakuni: Filtrlash va saralash
->when($request->integer('category_id'), ...) kategoriya berilmaganda nima qiladi?->orderBy('id') qo‘shiladi?2-topshiriq: Saralash parametrini tahlil qilish
URL dagi sort parametri vergul bilan ajratilgan ustunlar ro‘yxati: -price,name — avval narx bo‘yicha kamayish, keyin nom bo‘yicha o‘sish. Har bir qism trim qilinadi, bo‘sh qismlar e’tiborsiz qoldiriladi; bitta boshidagi - — desc, aks holda asc. Ustun $allowed oq ro‘yxatida bo‘lmasa, bitta ustun ikki marta uchrasa yoki ustunlar 3 tadan ko‘p bo‘lsa — InvalidArgumentException. Parametr null yoki faqat bo‘sh qismlardan iborat bo‘lsa — [[$default, 'asc']].
Imzo: function sort_parse(?string $param, array $allowed, string $default): array
Qaytaradi: Juftliklar ro‘yxati: [['price', 'desc'], ['name', 'asc']] — URL dagi tartibda.
sort_parse('-price', ['sku', 'name', 'price'], 'name')[["price","desc"]]
Sahifalash
paginate, simplePaginate, cursorPaginate
| Usul | SQL | Nima beradi | Qachon |
|---|---|---|---|
paginate(20) | count(*) + limit 20 offset N | Sahifa raqamlari, jami soni, lastPage() | Ma’lumotnomalar: mahsulotlar, kontragentlar |
simplePaginate(20) | limit 21 offset N (count yo‘q) | Faqat “Oldingi / Keyingi” | Katta ro‘yxat, jami son kerak emas |
cursorPaginate(20) | where id > ? order by id limit 21 | Kursor; sahifa raqami yo‘q | Millionlab qatorli jurnal, cheksiz aylantirish |
->withQueryString() va {{ $x->links() }} bilan ishlaydi.Sahifalash meta-ma’lumotini hisoblash
function meta(int $total, int $per, int $page): array { $last = max(1, (int) ceil($total / $per)); $from = ($page - 1) * $per + 1; $has = $total > 0 && $page <= $last; return [ 'current_page' => $page, 'last_page' => $last, 'from' => $has ? $from : null, 'to' => $has ? min($page * $per, $total) : null, ]; } echo json_encode(meta(137, 20, 1)), "\n"; echo json_encode(meta(137, 20, 7)), "\n"; echo json_encode(meta(0, 20, 1));
{"current_page":1,"last_page":7,"from":1,"to":20}
{"current_page":7,"last_page":7,"from":121,"to":137}
{"current_page":1,"last_page":1,"from":null,"to":null}last_page = 1nullfirstItem(), lastItem(), total(), lastPage()ProductTable: qidiruv URL da, filtr → 1-sahifa
class ProductTable extends Component { use WithPagination; #[Url(as: 'q', except: '')] public string $search = ''; public function updatedSearch(): void { $this->resetPage(); } public function render() { return view('livewire.product-table', [ 'products' => Product::with('category') ->search($this->search)->orderBy('name') ->paginate(20), ]); } }
/products?q=un&page=3 → qidiruv “gur” ga o‘zgardi /products?q=gur → 1-sahifa, jadval AJAX bilan yangilandi
Livewire\WithPagination — page URL da saqlanadiLivewire\Attributes\Url: $search ↔ ?q=; bo‘sh bo‘lsa URL da yo‘q$search o‘zgargandan keyin chaqiriladigan hookscopeSearch) — amaliyotda yozamizproduct-table.blade.php
<div> <input type="search" class="form-control" placeholder="SKU yoki nom bo‘yicha qidirish" wire:model.live.debounce.300ms="search"> <div wire:loading wire:target="search" class="small"> Qidirilmoqda… </div> <table class="table table-sm"> @foreach ($products as $p) <tr wire:key="product-{{ $p->id }}"> … </tr> @endforeach </table> {{ $products->links() }} </div>
Foydalanuvchi “un” yozdi → 300 ms kutiladi → bitta so‘rov “Qidirilmoqda…” → jadval va sahifalash yangilanadi
.live siz — keyingi harakatgacha kutadiwire:target — qaysi xossa uchun4-bo‘lim yakuni: Sahifalash
paginate va simplePaginate ning SQL darajasidagi farqi nima?stock_movements jurnali uchun qaysi sahifalash usuli mos va nima uchun?resetPage() chaqiriladi?3-topshiriq: Sahifalash havolalari oynasi
Sahifalash panelida hamma sahifa raqami ko‘rsatilmaydi. Har doim 1-sahifa, oxirgi sahifa va joriy sahifaning ikki tomonidagi $window tadan sahifa ko‘rsatiladi. Ko‘rsatiladigan qo‘shni raqamlar orasida faqat bitta sahifa tushib qolsa — o‘sha sahifa raqami qo‘yiladi, bittadan ko‘p bo‘lsa — '...'. $last < 1, $current 1..$last oralig‘ida bo‘lmasa yoki $window < 0 bo‘lsa — InvalidArgumentException.
Imzo: function sahifa_havolalari(int $current, int $last, int $window): array
Qaytaradi: O‘sish tartibidagi ro‘yxat: butun sonlar va '...' satrlari, masalan [1, '...', 8, 9, 10, 11, 12, '...', 20].
sahifa_havolalari(10, 20, 2)
[1,"...",8,9,10,11,12,"...",20]
Formalar va validatsiya
StoreProductRequest: ruxsat va qoidalar
class StoreProductRequest extends FormRequest { public function authorize(): bool { return $this->user()->can('products.manage'); } public function rules(): array { $product = $this->route('product'); // tahrirda — model return [ 'sku' => ['required', 'regex:/^[A-Z]{2}-\d{3}$/', Rule::unique('products')->ignore($product)], 'name' => ['required', 'string', 'max:150'], 'unit' => ['required', Rule::in(Product::UNITS)], 'price' => ['required', 'numeric', 'decimal:0,2', 'gt:0'], ]; } }
POST /products sku=un-1, price=0 302 → oldingi sahifa, sessiyada xatolar: sku: The sku field format is invalid. price: The price field must be greater than 0. (lang/uz/validation.php bilan — o‘zbekcha)
false bo‘lsa — 403; ruxsat nomi 5-mavzudan['dona', 'kg', 'litr', 'quti']min_stock uchun — integer|min:0old(), @error va @class bilan maydonlar
<form method="POST" action="{{ route('products.update', $product) }}"> @csrf @method('PUT') <label for="sku" class="form-label">SKU *</label> <input id="sku" name="sku" value="{{ old('sku', $product->sku) }}" @class(['form-control', 'is-invalid' => $errors->has('sku')])> @error('sku') <div class="invalid-feedback">{{ $message }}</div> @enderror <label for="price" class="form-label">Narx, so‘m *</label> <input id="price" name="price" inputmode="decimal" value="{{ old('price', $product->price) }}" @class(['form-control', 'is-invalid' => $errors->has('price')])> @error('price') <div class="invalid-feedback">{{ $message }}</div> @enderror <button class="btn btn-primary">Saqlash</button> </form>
Xato bo‘lsa: maydon qizil ramkada, ostida xabar, kiritilgan qiymat saqlanib qoladi (old). Muvaffaqiyat: 302 → /products, “Mahsulot UN-001 saqlandi”
_methodis-invalidOrderForm: massiv qoidalari va servis
class OrderForm extends Component { public ?int $counterpartyId = null; public array $lines = [['product_id' => null, 'quantity' => 1]]; protected function rules(): array { return [ 'counterpartyId' => 'required|exists:counterparties,id', 'lines.*.quantity' => 'required|integer|min:1', ]; } public function save(OrderService $orders) { $this->validate(); $order = $orders->create(OrderData::fromArray($this->all())); return $this->redirectRoute('orders.show', $order); } }
Xato: lines.0.quantity — The lines.0.quantity field must be at least 1. To‘g‘ri: draft buyurtma BY-2026-000124 → /orders/124
lines.*.product_id — exists:products,idrules() bo‘yicha; xatolar @error ga tushadi5-bo‘lim yakuni: Formalar va validatsiya
Dashboardlar
OmborPro dashboardi: kim nimani ko‘radi
Har bir kartochka — bitta savolga javob va bosilganda filtrlangan ro‘yxatga o‘tadi.
1Bugungi savdo
invoiced + shipped buyurtmalar summasi; kechagi kunga nisbatan % — menejer, admin2Tasdiqlash kutmoqda
confirmed holatidagi buyurtmalar soni → /orders?status=confirmed — menejer3Debitorlik
unpaid va partial hisob-fakturalar: total − paid_amount — buxgalter4Kam qoldiq
quantity − reserved < min_stock → /products?low=1 — omborchi57 kunlik savdo
KPI lar: SQL agregatlari va qisqa kesh
public function kpi(): array { return Cache::remember('dashboard:kpi', now()->addMinutes(5), fn () => [ 'sales_today' => Order::whereDate('created_at', today()) ->whereIn('status', ['invoiced', 'shipped']) ->sum('total'), 'pending' => Order::where('status', 'confirmed')->count(), 'debt' => Invoice::whereIn('status', ['unpaid', 'partial']) ->sum(DB::raw('total - paid_amount')), 'low_stock' => Stock::join('products', 'products.id', '=', 'stocks.product_id') ->whereRaw('quantity - reserved < products.min_stock') ->count(), ]); }
['sales_today' => '48750000.00', 'pending' => 7, 'debt' => '126400000.00', 'low_stock' => 12] 4 ta agregat so‘rov; keyingi 5 daqiqa — keshdan
Asia/Tashkent mintaqasidaRolga mos kartochka va 7 kunlik diagramma
<div class="row g-3"> @can('invoices.view') <x-kpi-card title="Debitorlik" :value="som($kpi['debt'])" :href="route('invoices.index', ['status' => 'unpaid'])" /> @endcan </div> <canvas id="sales7" height="120"></canvas> <script src="https://cdn.jsdelivr.net/npm/chart.js@4.4.1"></script> <script> new Chart(document.getElementById('sales7'), { type: 'line', data: { labels: @json($series->keys()), datasets: [{ label: 'Savdo, so‘m', data: @json($series->values()) }], }, }); </script>
Buxgalter: “Debitorlik 126 400 000 so‘m” kartochkasi + diagramma Omborchi: kartochka ko‘rinmaydi (invoices.view yo‘q)
resources/views/components/kpi-card.blade.php6-bo‘lim yakuni: Dashboardlar
Order::all() bilan hisoblash noto‘g‘ri?@can bilan kartochkani yashirish xavfsizlik uchun yetarlimi?Asosiy xulosalar
1Interfeys — ish joyi
2Holat URL da
3Saralash — faqat oq ro‘yxat
in_array(..., true) va ->orderBy('id') bilan barqaror tartib.4To‘g‘ri sahifalash
paginate — ma’lumotnoma, cursorPaginate — katta jurnal; withQueryString() va filtrda resetPage().5Validatsiya serverda
old(), @error, PRG; Livewire da wire:model.blur va massiv qoidalari.6Dashboard — harakat uchun
Yakunlashdan oldin sakkizta savol
wire:model modifikatorsiz qachon yuboriladi??sort=password ga to‘g‘ri munosabat?simplePaginate nima uchun tezroq?withQueryString() nima qiladi?{!! $p->name !!} xavfi?6-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
Filtrlarni saqlovchi query string
Filtrdan xavfsiz WHERE
Mahsulot formasini validatsiya qilish
Dashboard ko‘rsatkichlari
Ma’lumotlar jadvali: filtr + saralash + sahifa
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.
?sort= parametri bilan bog‘liq ikki xavfni va ularning yechimini yozing.