Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NCL-8675] Add latest Brew Push column to Group Build Builds list #486

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

patrikk0123
Copy link
Contributor

No description provided.

@patrikk0123
Copy link
Contributor Author

patrikk0123 commented Apr 24, 2024

Problems:

  • There is no WS message for Group Build push as a whole. Therefore, for each individual Build push WS message, the list is refetched (I added debounce to mitigate this)
  • Build push WS message contains no groupBuildId field

*
* @param requestConfig - Axios based request config
*/
export const getBuildsWithBrewPush = async (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dead code, it should be removed until it's really need

*
* @param requestConfig - Axios based request config
*/
export const getBuildsWithBrewPush = async (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Current implementation is blocking whole lits just because of one column, even if some users / use-cases don't need that column at all. Anyway soon we will be implementing the similar functionality on other top-level pages, where blocking way would be very limiting and probably not possible due to performance issues.

Possible solution could be creating separated latestBrewPush component managing its state independently?

I understand there can be some other technical difficulties, if so, feel free to reach me directly and we can investigate other possible solutions together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants