Inventaris

Setiap elemen yang dikirimkan oleh bundel, dan format yang digunakan untuk menyampaikannya. Tabel ini bukanlah daftar yang dipelihara oleh siapa pun: ini adalah registri setiap bundel yang dikirim, disusun dari deklarasinya dan diperiksa terhadap komponen-komponennya. Ini menjawab apa yang ada — tidak pernah apa yang seharusnya ada, yang merupakan pertanyaan yang tidak dapat diselesaikan oleh pemindaian mana pun dan yang harus dinyatakan oleh elemen itu sendiri.

Apa yang dihitung	Berapa banyak
Elemen ditemukan	131
Format yang perlu dikerjakan	541
Keputusan belum dibuat	0
Bentuk	61
Basis abstrak	6
Gaya	103
Template	91
Vue	100
Script	63
Skema	0
AI	0
React	0
Flutter	0

Elemen berdasarkan format

Satu baris per komponen, satu kolom per renderer. Sebuah komponen adalah direktori di bawah `components/` yang memuat setiap cara ia dapat digambar — `spinner/spinner.scss`, `spinner.html.twig`, `spinner.vue`, `spinner.ts` — sehingga tidak ada yang perlu mencocokkan empat direktori dengan nama lagi. Sebuah sel menghitung file di belakangnya — arahkan mouse ke salah satu untuk melihatnya. Setiap elemen yang dideklarasikan dibaca pada tingkat yang sama — sebuah baris yang ditemukan dalam satu format mungkin merupakan celah atau primitif yang tidak menginginkan yang lain, dan mengurutkan itu adalah pekerjaan yang ditujukan oleh tabel ini daripada sesuatu yang sudah diketahui. Empat status, dibedakan oleh siapa yang bergerak selanjutnya: sebuah cek, elemen ada di sana; sebuah peringatan, itu diinginkan dan hilang; sebuah lingkaran yang dicoret, itu tanpa sengaja; sebuah kosong, belum ada yang memutuskan. Arahkan mouse ke peringatan atau lingkaran untuk apa yang dikatakan deklarasi.

Elemen	Template	Vue
@WexampleSymfonyCodingBundle
`code-input`		2
`console`		2
`source-editor`		2
`source-findings`		2
`source-view`		2
@WexampleSymfonyDesignSystemBundle
`banner`	2	2
`bar`		2
`breadcrumb`		2
`button`		2
`button-link`		2
`button-menu`		2
`button-target`		2
`code-block`		2
collection/bar-list/`abstract-entity-bar-list`		2
collection/chat/`abstract-entity-chat`		2
collection/grid/`abstract-entity-grid`		2
collection/table/`abstract-entity-table`		2
collection/wall/`abstract-entity-wall`		2
`color-scheme-switch`
`confirm`
`content-image`		2
`copy-button`
`count-badge`
`data-table`		2
`date-display`		2
`dev-menu`
`diff`
`distribution`		2
`dock`	2
`document-embed`		2
`dots`		2
`dropzone`
`embed`
`fallback`
`file-explorer`		2
`file-path`		2
`filter-bar`		2
form/`button-input`		2
form/`checkbox-input`		2
form/`date-input`		2
form/`datetime-input`		2
form/`email-input`		2
form/`emoji-picker`		2
form/`file-input`		2
form/`hidden-input`		2
form/`number-input`		2
form/`otp-input`		2
form/`password-input`		2
form/`radio-input`		2
form/`range-input`		2
form/`select-input`		2
form/`submit-input`		2
form/`switch-input`		2
form/`tel-input`		2
form/`text-input`		2
form/`textarea-input`		2
form/`time-input`		2
form/`url-input`		2
form/`week-input`		2
`graph-log`		2
`image-crop`		2
`inline-svg`
`isolated`
`led`
`list-expanded`		2
`live-update-status`		2
`load-more`		2
`marker`		2
`media`		2
`menu-collapsible-panel`
`menu-item-collapsible`
`menu-item-link`		2
`menu-navigation`
`menu-separator`		2
`message`		2
`modal`	2
`overlay`	2
`page-tabs`
`pagination`		2
`panel`	2
`period-nav`		2
`progress-bar`		2
`properties`		2
`select`
`select-search`
`spinner`		2
`status-icon`		2
`stepper`		2
`switch`		2
`tab`		2
`tab-item`
`text-link`		2
`theme-select`
`timeline`		2
`toast`	2	2
`toast-stack`
`tool-dock`
`tooltip`
`tour`
`tree`		2
`tree-node`		2
`tree-row-directory`		2
`tree-row-file`		2
`upload-handler`
`wall`
`zone-collapsible`		2
`zone-resizer`		2
`zone-toolbar`
@WexampleSymfonyDesignSystemDemoBundle
collection/bar-list/`demo-bar-list`		2
collection/chat/`demo-entity-chat`		2
collection/table/`demo-compact-table`		2
collection/table/`demo-dates-table`		2
collection/table/`demo-entity-table`		2
collection/table/`demo-live-table`		2
collection/table/`demo-selectable-table`		2
collection/wall/`demo-entity-wall`		2
`demo-console`		2
`demo-dates`		2
`demo-distribution`		2
`demo-explorer`		2
`demo-file-explorer`		2
`demo-image-crop`		2
`demo-keyboard`		2
`demo-period`		2
`demo-progress`		2
`demo-status-icons`		2
`demo-tabs`		2
form/`demo-form`		2
search/`demo-search-box`		2
search/result/`demo-message`		2
search/result/`demo-room`		2

Abstrak

Lima basis di bawah `components/_abstract/`, yang tidak pernah digambar — mereka hanya diperluas. `_abstract/vue` adalah tiga blok twig kosong yang diisi oleh tiga puluh satu template; `_abstract/form-field` adalah apa yang dibangun oleh dua belas input. Mereka berada di luar matriks karena alasan yang sama seperti bentuk: mereka tidak dikirimkan kepada siapa pun, jadi meminta mereka untuk skema atau kembar react adalah meminta pertanyaan yang tidak dapat mereka jawab. Garis bawah mengatakan hal yang sama sebelum siapa pun membuka direktori. Apa yang ditampilkan adalah apa yang masing-masing sudah bawa kepada siapa pun yang memperluasnya.

Elemen	Gaya	Template	Vue	Script	Skema	AI	React	Flutter
`_abstract/form-field`
`_abstract/vue`
`_abstract/form`
`_abstract/vue-wrapper`
`_abstract/entity`
`_abstract/entity/bar`

Bentuk

Sebuah bentuk adalah gaya tanpa renderer: Anda menulis markup, menaruh kelas di atasnya, dan `@use` stylesheet dari milik Anda sendiri. `.stack`, `.grid`, `.block`, `.cluster`. Mereka terdaftar di sini dan tidak di tabel di atas karena tabel renderer tidak memiliki kolom untuk menawarkan sesuatu yang tidak memiliki — dan ketidakadaan mereka dari situ adalah mengapa semua peringatan berarti pekerjaan daripada pertanyaan yang diajukan dengan buruk. Garis ditarik oleh file, bukan oleh selera: sebuah bentuk adalah tepat satu `.scss` dan tidak ada yang merendernya, jadi ketika satu mendapatkan `.html.twig` itu pindah ke `components/` dan bergabung dengan matriks. Pindah itu adalah satu-satunya promosi yang ada. Apa yang masing-masing katakan tentang dirinya dibaca dari kepala stylesheet-nya sendiri, jadi tidak ada tempat kedua untuk mengalir darinya.

Bentuk	Apa fungsinya
`action-icon`	A muted icon button for a secondary action sitting in a corner — close, expand, dismiss —, its corners the controls' own: no button of the design system is round.
`action-link`	An inline link with an icon beside its label, muted until hovered, for a secondary action inside text or a row.
`avatar`	A round frame at text size holding a portrait, an icon or initials, cropped to fill.
`block`	The card: a raised rectangle with a title, a body, media, meta and a footer, each optional.
`chat`	A conversation — the thread of messages, their authors and dates, and the composer under it.
`cluster`	A row of small things that wraps when it runs out of room: tags, pills, buttons.
`container`	Centres its content and caps its width at one of the reading sizes.
`content`	Prose written elsewhere — an article, a description, rendered markdown — given spacing, headings and figures.
`corner-actions`	Icon actions in the corner of a framed thing — a code block, a lead, a block, a message —, out of the way until it is pointed at or reached by the keyboard.
`count`
`diff`	What changes, field by field: what it was and what it becomes, facing each other across an arrow — the value that goes struck, the one that stays in full. Read in a sync under review, a record's history, a change to confirm.
`disk-item`	A file or a directory shown as an icon with its name under it.
`disk-item-explorer`	The grid that lays disk items out, wrapping at a fixed item width.
`doc`	A documentation page: sections in two columns, the prose on one side and the code on the other.
`empty`	What stands where a list, a table or a panel has nothing to show: said once, in the middle of the room the rows would have taken, and quietly — nothing having happened is not an error.
`file-chip`	Files held by a field, one chip each: a thumbnail when it is an image, its kind's icon otherwise, its name — cut, whole in its title —, and the way to take it out. What a media picker shows of its choice, what a file field shows of the files dropped on it.
`flow`	The default vertical rhythm between blocks, and `no-flow` to drop it where it is unwanted.
`footer`	The strip closing a page, aligned on the same gutters as the rest of it.
`form`	Every form shape at once, for whoever draws a form and does not want to name them one by one.
`form/actions`	The row closing a form, where its buttons sit.
`form/addon`	A field with a fixed word beside its value — a unit, a currency — that is not part of it. The frame is the group's: it draws the field's border and ground, the input inside drops its own, so the word and the value sit in one field. The ring of focus goes round the whole, the frozen look too.
`form/assisted`	A field whose value is being filled for it, and how it reads while that happens.
`form/base`	What every input and textarea looks like before anything is said about it.
`form/checkbox`	A checkbox and its label, as a row that can be clicked whole.
`form/filter`	A field narrowing what is shown beside it — a table's rows, a menu's items, a folder's files: a magnifier and what is typed, in one frame. Written on a field with a word beside it (`form--input-group`), the magnifier being that word: <div class="form--input-group form--filter"> <span class="form--input-addon" aria-hidden="true">{{ icon('ph:bold/magnifying-glass') }}</span> <input class="form--input" type="search"> </div>
`form/inline`	A field and what acts on it, on one line: a message and its Send, a name and its Add, a search and its filter. The field takes the room, what acts on it keeps its width and never goes to another line — the shape a bar of options holds (shapes/toolbar), and a form of one question anywhere else.
`form/layout`	The frame of a form: its groups, their labels, and how they follow one another.
`form/messages`	The help text under a field, and the errors that replace it.
`form/password`	A password field and the control revealing what it holds.
`form/radio`
`form/select`	A native select made to read like the other inputs, caret included.
`form/state`	What a field looks like when it is focused, in error, or refusing input.
`form/stepper`	A number changed one step at a time — a quantity —: a button on each side of its figure. The figure keeps the width of a few digits, centred; the browser's own spinner, too small to aim at, is left out.
`form/surface`	Form fields set on a raised ground rather than on the page.
`form/switch`	A checkbox drawn as a switch.
`graph`	The frame a chart is drawn in, filling what it is given and clipping what overflows.
`grid`	Columns that fit themselves to the room available, or a fixed number when asked.
`gutters`	The horizontal and vertical margins a page keeps at its edges, shared so its parts line up.
`header`	The bar at the top of a page: its title, and the controls that belong to it.
`layout`	The frame of a page — a horizontal or vertical split, and a body that scrolls or does not.
`layout-reset-modern`	The reset: box model, margins, lists and typographic defaults, applied once to the document.
`lead`	An introductory paragraph, set apart in italics inside a dotted frame.
`media`	An image or a video held at a ratio — square, round, 16:9 — cropped rather than distorted.
`menu`	A menu, as a bar or as a column: its items, their icons, their counts and their submenus.
`meta-bar`	A thin line of secondary information between two separators, its groups pushed to either end.
`overlay-resizer`	The edges of a box that can be sized: strips lying across its border, drawn nothing — the cursor is what says the edge can be pulled.
`page`
`page-actions`	What a page does, at its foot: its actions in one row, whatever holds the page — a modal, a panel, an embed, the page's own zone. The first group stands at the start, the last one at the end: previous and next, cancel and save.
`page-loading`	A page on its way into the room it will fill — an embed today, a modal or a panel tomorrow: the manager wears `is-page-loading`, the page it held dims, and a spinner stands in the middle of the room.
`page-transition`	A page replaced by the next inside what holds it — a step of a tunnel in a modal: the one leaving slides a few pixels the way the visitor goes and fades, the one arriving comes in from the other side. Only a page marked `data-page-transition="slide"` moves; the classes are the page manager's.
`rail`	A column with a scrolling track between fixed ends, for a side panel or a toolbar of its own.
`stack`	Children laid in a row or a column with one gap, optionally split at a point or divided by rules.
`status-bar`	The line at the foot of what it describes — a listing, an editor, a card — saying where it stands: how many there are, which language, whether what is shown is saved. Read and never acted on: what is done to the thing is its footer's (`block--footer`), and what leads to it is a breadcrumb's. Its height is its own, the same empty or not, so what it sits under does not jump when a word comes and goes. The part said last, at the far end, is `status-bar--end`.
`surface`	The raised ground a block sits on, and the class that tells its children they are on one.
`table-sort`	A header that sorts — a table's, a listing's — is a button dressed as the header it sits in, so the row of labels reads the same sortable or not. The arrow is always there: a faint pair while the column does not order the list, one strong arrow once it does.
`timeline`	Things one under the other, each on a marker, joined by a line: the steps of a procedure, the events of a history, the stages of a run. What each holds is free — a title, a line of text, a table, a form — and the line runs down the whole height of it, to the next marker.
`toolbar`	A row of controls above or below what they act on, grouped and separated.
`upload-tray`	The rows of the uploads window: the design system's progress bar for each file — its name, how far it got —, and what came of it under it.
`wall`	Pictures of every height packed side by side with no holes, each one at its own ratio, as a photo wall is hung. The rows are a twelfth of a column's width, so a tile is as tall as its ratio says by spanning that many twelfths: `grid-row-end: span 9` for a 4:3 landscape — what wallSpan() and the wall template work out from a width and a height. Measuring a column needs the wall to be a container, which is why the tiles sit in a box of their own: a grid cannot read its own width. <div class="wall"> <div class="wall--tiles"> <a class="wall--tile media media--placeholder" style="grid-row-end: span 9">…</a> </div> </div>
`zone`	A region of a layout given its own size, splittable, scrollable, and never handing that size to its children.
`zone-table`	A zone given whole to a table: the table is the region, not a sheet laid in it. Whatever drives the table — its search, its filters, its bulk actions — stands at the top, its pages at the foot, both out of what scrolls; between them the table's own ground runs to the bottom of the zone however few rows there are, and the rows scroll under a header that stays. Any table of the system goes in it, written by the server or by a vue, with whatever holds it on the way — a collection, a mounted component: each of them, down to the table's frame, becomes a column handing its height on.

Apa yang ini tidak mencakup

Direktori `assets/` yang tidak dilalui oleh pemindaian, terdaftar dari disk daripada dari memori. Mixins, utilitas, dan token bukan elemen dan mungkin tidak pernah menjadi baris di sini; tata letak dan skrip bersama adalah, dan belum dicakup.

@WexampleSymfonyDesignSystemBundle/common@WexampleSymfonyDesignSystemBundle/css/fonts@WexampleSymfonyDesignSystemBundle/css/mixins@WexampleSymfonyDesignSystemBundle/css/partials@WexampleSymfonyDesignSystemBundle/css/primitives@WexampleSymfonyDesignSystemBundle/css/utilities@WexampleSymfonyDesignSystemBundle/fixtures@WexampleSymfonyDesignSystemBundle/js@WexampleSymfonyDesignSystemBundle/layouts@WexampleSymfonyDesignSystemBundle/partials@WexampleSymfonyDesignSystemDemoBundle/Common@WexampleSymfonyDesignSystemDemoBundle/Entity@WexampleSymfonyDesignSystemDemoBundle/Repository@WexampleSymfonyDesignSystemDemoBundle/forms@WexampleSymfonyDesignSystemDemoBundle/layouts@WexampleSymfonyDesignSystemDemoBundle/pages@WexampleSymfonyDesignSystemDemoBundle/partials@WexampleSymfonyCodingBundle/common@WexampleSymfonyCodingBundle/js

Dari mana ini berasal

Sebuah bundel ada di tabel karena menyatakannya — dengan mengimplementasikan `DesignSystemElementsBundleInterface`, cara bundel memberi tahu pemuat tentang jalur depannya. Setiap satu menulis `data/elements.json` di dalam asetnya sendiri, diterbitkan bersamanya, sehingga build, sisi node, bahasa lain atau agen semua bekerja dari file yang sama; halaman ini hanya merupakan persatuan mereka.

@WexampleSymfonyDesignSystemBundle@WexampleSymfonyDesignSystemDemoBundle@WexampleSymfonyCodingBundle