Skip to content

fix: react to provider set after the first update #565

Closed

Description

@uniqueg

Problem

Found while fixing the docs previews (#445, PR 564). Some components read provider only on their first update, which runs before React sets the property on a server-rendered element. Set later, provider is ignored, so the component never loads data:

  • service-registry: services, service
  • TRS: tools
  • TRS-Filer: tool-create

The Cloud Registry form (#502) and the WES components handle a provider set after the first update. The docs previews work around it by passing baseUrl, which these components do react to.

Proposal

Make these components react to provider changes after the first update, as the Cloud Registry form and the WES components do, with a test for a provider set after the first render.

Activity

  1. self-assigned this
    on Nov 13, 2026
  2. moved this to In progress in ELIXIR On-Cloudon Nov 13, 2026
  3. moved this from In progress to In review in ELIXIR On-Cloudon Nov 16, 2026
  4. moved this from In review to Done in ELIXIR On-Cloudon Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions