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

fix(endorsment-system): Add assets to project #16923

Merged
merged 2 commits into from
Nov 19, 2024

Conversation

rafnarnason
Copy link
Member

@rafnarnason rafnarnason commented Nov 18, 2024

Assets needed to style one-the-fly generated pdfs added to project json

Attach a link to issue if relevant

What

Specify what you're trying to achieve

Why

Specify why you need to achieve this

Screenshots / Gifs

Attach Screenshots / Gifs to help reviewers understand the scope of the pull request

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • New Features
    • Enhanced asset management by including all files from the designated assets directory during the build process, ensuring additional resources are available in the output.

@rafnarnason rafnarnason requested a review from a team as a code owner November 18, 2024 15:03
Copy link
Contributor

coderabbitai bot commented Nov 18, 2024

Walkthrough

The changes in this pull request introduce a new asset configuration in the services-endorsements-api project. This configuration specifies the inclusion of all files from the apps/services/endorsements/api/src/assets directory during the build process, directing them to the same output path. The overall project configuration remains unchanged, with no impacts on existing targets or executors.

Changes

File Path Change Summary
apps/services/endorsements/api/project.json Added asset configuration to the build target to include all files from src/assets directory.

Possibly related PRs

  • fix(service-portal): petitions - export list #16850: The changes in this PR involve modifications to the EndorsementListService class, specifically in the createDocumentBuffer method, which is relevant to asset management and document generation, similar to the asset configuration changes in the main PR.

Suggested labels

automerge

Suggested reviewers

  • kksteini

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@rafnarnason rafnarnason requested a review from a team November 18, 2024 15:03
Copy link

codecov bot commented Nov 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.46%. Comparing base (b3e05fd) to head (592d36d).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #16923   +/-   ##
=======================================
  Coverage   36.46%   36.46%           
=======================================
  Files        6903     6903           
  Lines      144583   144550   -33     
  Branches    41283    41269   -14     
=======================================
- Hits        52718    52714    -4     
+ Misses      91865    91836   -29     
Flag Coverage Δ
api 3.34% <ø> (ø)
application-system-api 41.02% <ø> (ø)
services-endorsements-api 53.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 5 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3e05fd...592d36d. Read the comment docs.

---- 🚨 Try these New Features:

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (1)
apps/services/endorsements/api/project.json (1)

37-41: Consider restructuring the output path

The current configuration uses the same path for both input and output, which differs from the pattern used by other assets in this configuration. This might cause confusion during builds and deployment.

Consider applying this diff to align with the project's asset organization pattern:

   {
     "glob": "*",
     "input": "apps/services/endorsements/api/src/assets",
-    "output": "apps/services/endorsements/api/src/assets"
+    "output": "./pdf-assets"
   }
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 760b5fe and 925e62d.

📒 Files selected for processing (1)
  • apps/services/endorsements/api/project.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/services/endorsements/api/project.json (2)

Pattern apps/services/**/*: "Confirm that the code adheres to the following:

  • NestJS architecture, including modules, services, and controllers.
  • Dependency injection patterns and service encapsulation.
  • Integration and unit testing coverage and practices."

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."

apps/services/endorsements/api/project.json Show resolved Hide resolved
@datadog-island-is
Copy link

datadog-island-is bot commented Nov 18, 2024

Datadog Report

All test runs 97cc89f 🔗

4 Total Test Services: 0 Failed, 4 Passed
➡️ Test Sessions change in coverage: 5 no change

Test Services
Service Name Failed Known Flaky New Flaky Passed Skipped Total Time Code Coverage Change Test Service View
api 0 0 0 4 0 3.03s 1 no change Link
application-system-api 0 0 0 112 2 3m 31.18s 1 no change Link
application-template-api-modules 0 0 0 67 0 0s N/A Link
services-endorsements-api 0 0 0 42 0 46.11s 1 no change Link

Copy link
Member

@eirikurn eirikurn left a comment

Choose a reason for hiding this comment

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

Approving with comment. You should run yarn build services-endorsements and see correct results in the dist folder.

apps/services/endorsements/api/project.json Show resolved Hide resolved
@rafnarnason rafnarnason added the automerge Merge this PR as soon as all checks pass label Nov 19, 2024
@kodiakhq kodiakhq bot merged commit d743d2e into main Nov 19, 2024
37 of 38 checks passed
@kodiakhq kodiakhq bot deleted the endorsement-system/assets-config branch November 19, 2024 10:20
jonnigs pushed a commit that referenced this pull request Nov 26, 2024
Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this PR as soon as all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants