Feature/creatives table sectors page #21
Open
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.
The table used in brands for creative table was used. To use the backend services, a hook was created, in such a way that all the logic is in that hook and the component is only responsible for calling it and rendering the child components.
For the new "Sectors" view, the same thing was done, two hooks to have the services and both responses were waited to be able to unify them and show them in the view. Another way to do it would be to render the cards with the data from the endpoint that responds first and then fill them with the missing data when the 2nd endpoint responds.
The component used in other views was used for loading.
For the error state, a different view was not implemented but it can be done by only calling the corresponding service and not loading the entire view as the current error component does.