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

feat: added news about un-deploy #14663

Merged
merged 5 commits into from
Feb 14, 2025
Merged

feat: added news about un-deploy #14663

merged 5 commits into from
Feb 14, 2025

Conversation

framitdavid
Copy link
Collaborator

@framitdavid framitdavid commented Feb 14, 2025

Description

added news about un-deploy

Related Issue(s)

  • PR itself

Verification

  • Your code builds clean without any errors or warnings
  • Manual testing done (required)

Summary by CodeRabbit

  • New Features
    • Introduced a news update informing users about the new ability to unpublish apps. The update provides guidance on key considerations and details the unpublishing process, with relevant documentation available during the procedure.

Copy link
Contributor

coderabbitai bot commented Feb 14, 2025

📝 Walkthrough

Walkthrough

A new entry has been added to a JSON file under the news content component. The added item in the "news" array includes a specific date, an empty title field, and detailed content that informs users about the unpublishing process for apps along with associated documentation.

Changes

File Path Change Summary
frontend/app-development/features/overview/components/News/NewsContent/news.nb.json Added a new entry to the "news" array with a "date": "2025-02-14", an empty "title", and a "content" field explaining the unpublishing process and reference to documentation.

Suggested labels

skip-releasenotes, added-to-sprint

Suggested reviewers

  • Ildest
  • Jondyr

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 73a78d0 and 17cd4c8.

📒 Files selected for processing (1)
  • frontend/app-development/features/overview/components/News/NewsContent/news.nb.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • frontend/app-development/features/overview/components/News/NewsContent/news.nb.json

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@github-actions github-actions bot added solution/studio/designer Issues related to the Altinn Studio Designer solution. area/overview Area: Related to the overview page frontend labels Feb 14, 2025
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: 0

🧹 Nitpick comments (1)
frontend/app-development/features/overview/components/News/NewsContent/news.nb.json (1)

4-8: Add a title for the news entry.

Other news entries in the file have descriptive titles. Consider adding a title that summarizes the un-deploy feature, similar to the format used in other entries.

    {
      "date": "2025-02-13",
-      "title": "",
+      "title": "Nå kan du avpublisere apper!",
      "content": "Vi har nå gjort det mulig å avpublisere apper. Du finner informasjon om hva du må tenke på før du avpubliserer og hvordan du gjør det i dokumentasjonen vår. Denne informasjonen er også tilgjengelig underveis i avpubliseringsprosessen."
    },
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7dcd0d7 and 05ff1ac.

📒 Files selected for processing (1)
  • frontend/app-development/features/overview/components/News/NewsContent/news.nb.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Build environment and run e2e test
  • GitHub Check: Testing
  • GitHub Check: CodeQL
🔇 Additional comments (1)
frontend/app-development/features/overview/components/News/NewsContent/news.nb.json (1)

2-2:

❓ Verification inconclusive

Verify JSON schema compliance.

The file references a schema file. Let's verify that the new entry complies with the schema.


🏁 Script executed:

#!/bin/bash
# Description: Check if the schema file exists and validate the JSON against it
fd --type f "news.schema.json" --exec cat {} \;

Length of output: 974


Schema file verified – please confirm complete JSON compliance

  • The news.schema.json file was located successfully, and its content confirms it defines a valid JSON schema for news items (requiring date, title, and content with proper formats).
  • The $schema property in news.nb.json correctly references this schema.
  • To fully validate the new entry, ensure that the JSON data in news.nb.json (beyond the $schema reference) conforms to the schema’s requirements (e.g., proper date format and inclusion of all required fields).

Copy link
Contributor

@Ildest Ildest left a comment

Choose a reason for hiding this comment

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

Manglet en r på "får" bare.

Copy link

codecov bot commented Feb 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.76%. Comparing base (7dcd0d7) to head (17cd4c8).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #14663   +/-   ##
=======================================
  Coverage   95.76%   95.76%           
=======================================
  Files        1914     1914           
  Lines       24961    24961           
  Branches     2858     2858           
=======================================
  Hits        23904    23904           
  Misses        799      799           
  Partials      258      258           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@framitdavid framitdavid added the skip-manual-testing PRs that do not need to be tested manually label Feb 14, 2025
@framitdavid framitdavid enabled auto-merge (squash) February 14, 2025 09:30
Copy link
Contributor

@Ildest Ildest left a comment

Choose a reason for hiding this comment

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

Tipp, topp tommel opp :-)

@framitdavid framitdavid merged commit 502c440 into main Feb 14, 2025
12 checks passed
@framitdavid framitdavid deleted the feat/undeploy-news branch February 14, 2025 10:03
{
"date": "2025-02-14",
"title": "",
"content": "Vi har nå gjort det mulig å avpublisere apper. Du får informasjon underveis, om hva du må tenke på før du avpubliserer. Du kan også lese om hvordan du gjør det i dokumentasjonen vår."
Copy link
Contributor

Choose a reason for hiding this comment

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

Er det et mellomrom for mye etter Vi?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/overview Area: Related to the overview page frontend skip-manual-testing PRs that do not need to be tested manually solution/studio/designer Issues related to the Altinn Studio Designer solution.
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

2 participants