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: Branding changes are not getting applied on release-ee. Not working on local pull either #29159

Merged
merged 2 commits into from
Nov 28, 2023

Conversation

jsartisan
Copy link
Contributor

@jsartisan jsartisan commented Nov 28, 2023

Fixes #29140

Summary by CodeRabbit

  • New Features
    • Enhanced the TenantApi to allow custom Axios configurations when updating tenant settings, improving flexibility and usability.
  • Bug Fixes
    • Improved error handling in the updateTenantConfig method to ensure more reliable API interactions.

@github-actions github-actions bot added Widgets Product This label groups issues related to widgets Branding Product All issues under branding and whitelabelling appsmith ecosystem Bug Something isn't working Needs Triaging Needs attention from maintainers to triage Release Release Blocker This issue must be resolved before the release labels Nov 28, 2023
@jsartisan
Copy link
Contributor Author

/ok-to-test

Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7016133972.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 29159.

Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7016137686.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 29159.

Copy link

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7016133972.
Commit: ``.
Cypress dashboard url: Click here!
It seems like there are some failures 😔. We are not able to recognize it, please check this manually here.

Copy link

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7016137686.
Commit: ``.
Cypress dashboard: Click here!
The following are new failures, please fix them before merging the PR:

  1. cypress/e2e/Sanity/Datasources/MockDBs_Spec.ts

To know the list of identified flaky tests - Refer here

@jsartisan
Copy link
Contributor Author

/ok-to-test

Copy link

Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/7017370104.
Workflow: Appsmith External Integration Test Workflow.
Commit: ``.
PR: 29159.

Copy link

Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/7017370104.
Commit: ``.
Cypress dashboard url: Click here!
All cypress tests have passed 🎉🎉🎉

@somangshu somangshu merged commit 93c173c into release Nov 28, 2023
15 of 16 checks passed
@somangshu somangshu deleted the fix/axios-branding-bug branch November 28, 2023 11:32
@Nikhil-Nandagopal Nikhil-Nandagopal added Platform Administration Pod Issues related to platform administration & management and removed Widgets Product This label groups issues related to widgets labels Aug 6, 2024
Copy link
Contributor

coderabbitai bot commented Aug 6, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

The recent changes to the TenantApi enhance API functionality by introducing a new optional property, apiConfig, within the UpdateTenantConfigRequest interface. This allows custom Axios configurations during tenant updates. The updateTenantConfig method has been updated to utilize this new property, improving flexibility and control over API requests.

Changes

File Change Summary
app/client/src/ce/api/TenantApi.ts Modified UpdateTenantConfigRequest to include an optional apiConfig property; updated updateTenantConfig method to utilize this new parameter.

Assessment against linked issues

Objective Addressed Explanation
Branding changes not applied (Issue #29140) Changes made are unrelated to branding functionality.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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 the QA Needs QA attention label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Branding Product All issues under branding and whitelabelling appsmith ecosystem Bug Something isn't working Needs Triaging Needs attention from maintainers to triage Platform Administration Pod Issues related to platform administration & management QA Needs QA attention Release Blocker This issue must be resolved before the release Release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Branding changes are not getting applied on release-ee. Not working on local pull either
4 participants