[GEN-2041]: fix auto-fill indicator for destinations #2018
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several updates to the
frontend/webapp/containers/main/destinations
directory, focusing on enhancing theDestinationFormBody
component and improving the export structure of theDestinationsList
component. The most important changes include adding new hooks and logic to handle auto-filling of dynamic fields, modifying the component structure for consistency, and updating export statements.Enhancements to
DestinationFormBody
component:useEffect
anduseRef
hooks to handle the auto-filling check for dynamic fields and set theautoFilled
state accordingly. [1] [2]DestinationFormBody
component to be a functional component using arrow function syntax for consistency. [1] [2]Improvements to
DestinationsList
component:DestinationsList
component to be exported directly instead of using a separate export statement. [1] [2]