Skip to content

Command Summary - New UI#186

Merged
EyalDelarea merged 39 commits intojfrog:masterfrom
EyalDelarea:improve_summary_ui
Sep 1, 2024
Merged

Command Summary - New UI#186
EyalDelarea merged 39 commits intojfrog:masterfrom
EyalDelarea:improve_summary_ui

Conversation

@EyalDelarea
Copy link
Copy Markdown
Contributor

@EyalDelarea EyalDelarea commented Aug 18, 2024

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • I used npm run format for formatting the code before submitting the pull request.

This PR removes the logic to combine each markdown section from the setup-cli to the CLI itself, because of the newly introduced command jf generate-command-summary

It uses an unreleased CLI command so the tests will fail until the new command will be released.

Depends on jfrog/jfrog-cli#2653

@EyalDelarea EyalDelarea added the improvement Automatically generated release notes label Aug 18, 2024
@EyalDelarea EyalDelarea changed the title Update Job Summary UI Command Summary - Move logic to CLI Aug 18, 2024
@EyalDelarea EyalDelarea requested a review from eyalbe4 August 26, 2024 11:49
@EyalDelarea EyalDelarea marked this pull request as ready for review August 26, 2024 11:50
lib/utils.js Outdated
}
catch (error) {
throw new Error('failed to read section file: ' + fullPath + ' ' + error);
core.debug("No markdown file found in the job's output directory.");
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

  • It is best to add the error message to the log message. The same goes for logging in the isHeaderPngAccessible function.
  • Since the error can be thrown for a variety of reasons, and not just in case the file doesn't exist, perhaps it would be better to add a specific check for the existence of the file before reading it. That is, if our code actually expects a scenario where the file shouldn't exist. If the code doesn't expect such a scenario, then the logging here should an error log and not a debug one.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@eyalbe4,

I'm not sure we should fail the entire build by this post-cleanup errors. Maybe i'm wrong, but it's an extra feature that is nice to have but if something goes wrong i'm not sure i want to effect the entire build, let's discuss it.

About isHeaderPngAccessible , this is purely optional and i'd rather display the fallback banner then to fail the entire build.

@EyalDelarea EyalDelarea mentioned this pull request Sep 1, 2024
2 tasks
@EyalDelarea EyalDelarea changed the title Command Summary - Move logic to CLI Command Summary - New UI Sep 1, 2024
@EyalDelarea EyalDelarea added new feature Automatically generated release notes and removed improvement Automatically generated release notes labels Sep 1, 2024
@EyalDelarea EyalDelarea added the safe to test Approve running integration tests on a pull request label Sep 1, 2024
@github-actions github-actions bot removed the safe to test Approve running integration tests on a pull request label Sep 1, 2024
@EyalDelarea EyalDelarea merged commit c462cde into jfrog:master Sep 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new feature Automatically generated release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants