mirror of
https://github.com/blakeblackshear/frigate.git
synced 2026-07-04 11:01:14 +03:00
0bdf5002a0
* use monotonic clock for detector inference duration to prevent negative values from wall clock steps * add ability to set camera's webui_url from camera management pane * Gemini send thought signature * Update docs * copy face and lpr configs from source camera to replay camera * add guard * improve dummy camera docs * remove version number * fix stale field message after reverting a conditional form field Routes field-level conditional messages through a dedicated React Context instead of merging them into uiSchema. RJSF's Form keeps state.uiSchema sticky across renders during processPendingChange (formData is updated, uiSchema is not), so a previously injected ui:messages array stays attached to a field even after the triggering condition flips back to false. Context propagation re-runs FieldTemplate directly on every provider value change, sidestepping that staleness. * add semantic search field message to note that model_size is irrelevant when embeddings provider is selected --------- Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>
14 lines
677 B
TypeScript
14 lines
677 B
TypeScript
import { createContext } from "react";
|
|
import type { FieldConditionalMessage } from "./section-configs/types";
|
|
|
|
// Provides currently-active field messages to FieldTemplate without going
|
|
// through RJSF's per-field uiSchema. RJSF caches state.uiSchema across renders
|
|
// in a way that can leave stale ui:messages attached to a field when the
|
|
// triggering condition flips back to false (see processPendingChange in
|
|
// @rjsf/core Form.js — formData is updated immediately, uiSchema is not).
|
|
// useContext re-runs consumers directly on provider value change, sidestepping
|
|
// that staleness.
|
|
export const FieldMessagesContext = createContext<FieldConditionalMessage[]>(
|
|
[],
|
|
);
|