Feature Request: Enhancing <CheckForApplicationUpdate> for module federation apps

[smeng9]

Is your feature request related to a problem? Please describe.

1. Our application uses the module federation design but the <CheckForApplicationUpdate> can only check for a single url. It cannot check multiple urls for each module

2. Additionally the fetch function in getHashForUrl

   react-admin/packages/ra-core/src/util/useCheckForApplicationUpdate.ts

   Line 61 in f030350

   const response = await fetch(url);

   does not support passing additional options like cache control, so even after the interval has passed, it may check for a stale copy of data from cache which breaks the purpose of CheckForApplicationUpdate. This may be a bug.

3. We would also like an additional callback function handleApplicationUpdate passed into the <CheckForApplicationUpdate> so we can customize the button click behavior

   react-admin/packages/ra-ui-materialui/src/layout/ApplicationUpdatedNotification.tsx

   Line 17 in f030350

   const handleButtonClick = () => {

   like making backup of localstorage, give user warning about potential data loss, etc.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Enhance the <CheckForApplicationUpdate> interface to make url support an array of strings, add the fetch options object, and add the callback.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Stack a bunch of CheckForApplicationUpdate in the layout, each checking for a single url. However that would not solve problem 2 and 3.
Hope these enhancement can benefit other people so they don't have to reimplement the react hooks.

Additional context
Add any other context or screenshots about the feature request here.

[fzaninotto]

Hi, and thanks for your feedback.

Regarding your points:

1. The CheckForApplicationUpdate component won't support module federation. You will have to build your own component for that.
2. We're open to a PR adding the support for an options prop passed as second argument to fetch
3. It's already possible: the parameter is called onNewVersionAvailable. We do need to document it, though, so I'm marking this as a documentation issue.