@medplum/react 4.5.2 → 5.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cjs/index.cjs +2 -2
- package/dist/cjs/index.cjs.map +2 -2
- package/dist/cjs/index.d.ts +0 -15
- package/dist/esm/index.d.ts +0 -15
- package/dist/esm/index.mjs +3 -3
- package/dist/esm/index.mjs.map +2 -2
- package/package.json +27 -30
package/dist/cjs/index.d.ts
CHANGED
|
@@ -930,21 +930,6 @@ export declare interface MedplumProviderProps {
|
|
|
930
930
|
|
|
931
931
|
export declare const MemoizedFhirPathTable: MemoExoticComponent<typeof FhirPathTable>;
|
|
932
932
|
|
|
933
|
-
/**
|
|
934
|
-
* @deprecated
|
|
935
|
-
*
|
|
936
|
-
* The memoization `MemoizedSearchControl` provides has been merged into `SearchControl`. Previously the memoization was done via HOC but
|
|
937
|
-
* it was proven that this wasn't effective for a large number of use cases, especially when:
|
|
938
|
-
* 1. `search` was an inline static object, which would trigger the memo to recompute on every re-render of the parent component
|
|
939
|
-
* 2. Any of the callbacks, such as `onClick` were not memoized via `useCallback`, which would result in the recomputation as well
|
|
940
|
-
*
|
|
941
|
-
* Scenario 1 also retriggered the effect that runs `loadResults` on change of the `search`, which was less than desirable.
|
|
942
|
-
*
|
|
943
|
-
* The memoization is now accomplished via checking deep equality of the incoming `search` prop in the body of the component, and setting a memoized
|
|
944
|
-
* state whenever the incoming and current memoized value are not deeply equal. See: https://github.com/medplum/medplum/pull/5023
|
|
945
|
-
*/
|
|
946
|
-
export declare const MemoizedSearchControl: typeof SearchControl;
|
|
947
|
-
|
|
948
933
|
export declare function MfaForm(props: MfaFormProps): JSX.Element;
|
|
949
934
|
|
|
950
935
|
export declare type MfaFormFields = 'token';
|
package/dist/esm/index.d.ts
CHANGED
|
@@ -930,21 +930,6 @@ export declare interface MedplumProviderProps {
|
|
|
930
930
|
|
|
931
931
|
export declare const MemoizedFhirPathTable: MemoExoticComponent<typeof FhirPathTable>;
|
|
932
932
|
|
|
933
|
-
/**
|
|
934
|
-
* @deprecated
|
|
935
|
-
*
|
|
936
|
-
* The memoization `MemoizedSearchControl` provides has been merged into `SearchControl`. Previously the memoization was done via HOC but
|
|
937
|
-
* it was proven that this wasn't effective for a large number of use cases, especially when:
|
|
938
|
-
* 1. `search` was an inline static object, which would trigger the memo to recompute on every re-render of the parent component
|
|
939
|
-
* 2. Any of the callbacks, such as `onClick` were not memoized via `useCallback`, which would result in the recomputation as well
|
|
940
|
-
*
|
|
941
|
-
* Scenario 1 also retriggered the effect that runs `loadResults` on change of the `search`, which was less than desirable.
|
|
942
|
-
*
|
|
943
|
-
* The memoization is now accomplished via checking deep equality of the incoming `search` prop in the body of the component, and setting a memoized
|
|
944
|
-
* state whenever the incoming and current memoized value are not deeply equal. See: https://github.com/medplum/medplum/pull/5023
|
|
945
|
-
*/
|
|
946
|
-
export declare const MemoizedSearchControl: typeof SearchControl;
|
|
947
|
-
|
|
948
933
|
export declare function MfaForm(props: MfaFormProps): JSX.Element;
|
|
949
934
|
|
|
950
935
|
export declare type MfaFormFields = 'token';
|