@autobusal/admin-agents 1.2.0 → 1.2.2

package/Manage.tsx

@@ -29,7 +29,20 @@ const Manage = ({ url, t }: Props): JSX.Element => {
 
   const { data, isFetching } = useGetAgent(id);
   
-  const title = id > 0 ? t('admin_agents.manage.title.update', { company: data?.company, ns: 'common' }) : t('admin_agents.manage.title.new', { ns: 'common' });
+  /*
+   * Claude - 2026-08-29 (audit A4-09, low)
+   *
+   * THE COMPANY AND THE ACCOUNT IT BELONGS TO. This screen is addressed by
+   * `agents`.`id` while /account/funds/manage is addressed by `users`.`id`,
+   * so the same number in the URL opens two different agencies on the two
+   * screens - demonstrated live in the audit, where a credit limit was set on
+   * an agency nobody meant to touch. Company names are not unique either
+   * (three separate agencies are registered as "API Company"), so the
+   * heading alone could not say which record was open. The email can.
+   */
+  const company = [data?.company, data?.user?.email].filter(Boolean).join(' · ');
+
+  const title = id > 0 ? t('admin_agents.manage.title.update', { company, ns: 'common' }) : t('admin_agents.manage.title.new', { ns: 'common' });
 
   useBreadcrumbs(title, [{ name: t('admin_agents.browse.title', { ns: 'common' }), url }]);
 

package/package.json

@@ -1,7 +1,10 @@
 {
   "name": "@autobusal/admin-agents",
-  "version": "1.2.0",
+  "version": "1.2.2",
   "author": "Ferjolt Ozuni",
   "type": "module",
-  "main": "index.ts"
+  "main": "index.ts",
+  "publishConfig": {
+    "access": "public"
+  }
 }

package/services.ts

@@ -1,4 +1,4 @@
-import { UseMutationResult, UseQueryResult, UseSuspenseQueryResult, useMutation, useQuery, useSuspenseQuery } from '@tanstack/react-query';
+import { UseMutationResult, UseQueryResult, UseSuspenseQueryResult, useMutation, useQuery, useSuspenseQuery, useQueryClient } from '@tanstack/react-query';
 import { apiClient } from '@autobusal/providers';
 import { PaginationData } from '@autobusal/providers/types/pagination';
 import { AgentData } from '@autobusal/providers/types/agents';
@@ -36,9 +36,19 @@ export const useGetAgent = (id: number): UseSuspenseQueryResult<AgentData> => (
   })
 );
 
-export const usePostAgent = (id: number): UseMutationResult<void, Error, AgentData, unknown> => (
-  useMutation({
+export const usePostAgent = (id: number): UseMutationResult<void, Error, AgentData, unknown> => {
+  const queryClient = useQueryClient();
+
+  return useMutation({
     mutationKey: ['admin-agents-save', { id }],
+    // Claude - 2026-09-06: re-read the record after a save. With Save & Stay
+    // the page stays on stale data, and the one field that only the server
+    // can fill in - the URL of an image just uploaded - never appeared
+    // until a reload. The list is refreshed too, for the same reason.
+    onSuccess: () => {
+      queryClient.invalidateQueries({ queryKey: ['admin-agents-manage', { id }] });
+      queryClient.invalidateQueries({ queryKey: ['admin-agents'] });
+    },
     mutationFn: async (data: AgentData) => {
       const formData = new FormData();
 
@@ -69,8 +79,8 @@ export const usePostAgent = (id: number): UseMutationResult<void, Error, AgentDa
           response.data
         ));
     }
-  })
-);
+  });
+};
 
 export const useDeleteAgent = (): UseMutationResult<void, Error, number, unknown> => (
   useMutation({

package/CHANGELOG.md

@@ -1,52 +0,0 @@
-# Changelog
-
-## 1.2.0 (2026-08-29)
-
-- Editors offer Save & Close alongside Save & Stay, so correcting a record no longer bounces you back to its list every time (opt-in per page, editing only).
-
-## 1.1.7 (2026-08-28)
-
-- Company minimum length 2, matching the server rule - two-letter brand names can be saved (sweep #56).
-
-## 1.1.6
-
-### Fixed
-
-- **License No. is optional on the manage form.** The agent sign-up stopped collecting it on 2026-08-07 and the column is nullable server-side, but the form's required rule made approving a self-registered agency impossible without inventing a number. (Audit AUTH-02b.)
-
-## 1.1.5
-
-### Added
-
-- **Credit limit on the agent form.** Ordinary website agents can now sell
-  postpaid: obtapi's funds gate measures the balance's resting position -
-  funds minus (amount less commission) - against `-credit_limit` instead of
-  refusing anything below the gross total. 0 keeps the historic prepaid
-  behaviour; a positive number lets the balance run down to -that-much,
-  restored when an admin records the agent's payment on the funds screen.
-
-## [1.1.4] - 2026-08-07
-
-### Fixed
-
-- **Country select no longer defaults to Afghanistan.** `value` was `?? 0`,
-  which matches no country, so opening an agent with none on file and
-  pressing save filed them in Afghanistan.
-
-
-## 1.1.3
-
-### Changed
-
-- **Address is a single-line input, not a textarea**, matching the other
-  address fields across the apps.
-
-All notable changes to this package are documented here. This project follows [Keep a Changelog](https://keepachangelog.com/) and [Semantic Versioning](https://semver.org/).
-
-## [1.1.2] - 2026-07-19
-
-### Fixed
-
-- `Manage.tsx`: the agent edit form's email field is now hydrated with the existing value (`value: data?.user.email`). Previously the email `<input>` rendered empty when editing an agent, so the field appeared blank and a save could overwrite the stored email with an empty value.
-
-Authored by Ferjolt Ozuni. Consolidated from the magus and alvavel whitelabel patch sets into canonical @autobusal source (eliminates per-repo patch-package divergence).