Viewing as leads the Roles rail; settings get a rail, agent cards, one Sources section at a time
A search agent is a persona, and every like or pass belongs to the one being viewed. The rail now opens on Viewing as: a full-width chooser, the name alone with one agent, a note with none, remembered in the URL and localStorage. The vote buttons, the reader's affinity control, the feed, the tag counts and the reader fetch all carry that agent; before, votes sent none and every one landed on the default agent. Best first and Newest first are back as the segmented control under Order, independent of the agent. The rail selects no longer clip descenders: Chrome ignores line-height on a select, so the fixed box is gone in favour of padding and a min-height. Settings render inside a sticky rail (Search agents; Sources with Job boards, Company boards, Runs, Messages; Account), a strip under the header on a phone, so Runs is one click away however long the company list gets. Sources shows one section at a time, chosen by the fragment, so the old redirects still land. Search agents are cards, newest first: name, an On/Off switch with its word, the intent in full, the weights, Edit in place, New agent on top, and a link to Roles as that agent. Switching one on rescores it. replace_scores writes nothing for an agent deleted while score was running, instead of failing the run on the foreign key. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
063771d617
commit
c4f2bcc0c9
20 files changed
+836
-326
No files matched your search
@@ -8,6 +8,12 @@
|
||||
renders only the select options, from `app.models` and
|
||||
`plugins.ats.FUNCTIONS`, so they cannot drift from what the store accepts.
|
||||
|
||||
The rail opens on Viewing as: which search agent the feed is seen as.
|
||||
An agent is a persona (a candidate, a hiring manager watching the market)
|
||||
with its own scores, votes and hidden companies, so the order, the stance
|
||||
on each row and every vote cast belong to the agent picked here. Order is
|
||||
its own section below, the same two choices whichever agent is picked.
|
||||
|
||||
`/roles/{uid}` renders this same page with `role` set: the reader starts
|
||||
open, so a phone lands on the role rather than on the list for as long as
|
||||
the script takes. No `data-rail` on `<body>` until the script sets one:
|
||||
@@ -33,6 +39,14 @@
|
||||
|
||||
<div class="shell">
|
||||
<aside id="rail" aria-label="Filters">
|
||||
<section class="rail-viewing" aria-labelledby="viewing-as">
|
||||
{# One agent is its name, two or more a select, none a sentence with
|
||||
the way to make one. The script shows whichever applies. #}
|
||||
<h3 id="viewing-as">Viewing as <a class="linky" href="/settings/agents">agents</a></h3>
|
||||
<select id="agent" class="rail-select agent-pick" aria-labelledby="viewing-as" hidden></select>
|
||||
<p id="agent-one" class="agent-pick" hidden></p>
|
||||
<p id="agent-none" class="rail-note" hidden></p>
|
||||
</section>
|
||||
<section>
|
||||
<h3>Filters</h3>
|
||||
<button type="button" class="rail-row" id="show-read" aria-pressed="true"
|
||||
@@ -40,11 +54,10 @@
|
||||
class="count" aria-hidden="true">👁</span></button>
|
||||
</section>
|
||||
<section>
|
||||
<h3>Order and period</h3>
|
||||
{# Best first and Newest first. With more than one ranking enabled the
|
||||
segmented control gives way to the select, one entry per ranking. #}
|
||||
<h3>Order</h3>
|
||||
{# Best first is the viewing agent's score, Newest first is first seen;
|
||||
both carry that agent's votes. #}
|
||||
<div class="seg" id="sort" role="group" aria-label="Order"></div>
|
||||
<select id="agent" class="rail-select" aria-label="Order" hidden></select>
|
||||
<label class="rail-field" for="period">First seen</label>
|
||||
<select id="period" class="rail-select"></select>
|
||||
</section>
|
||||
|
||||
Reference in new issue
Block a user