chore: remove hidden flag from linkedin audience

[ItsSudip]

What are the changes introduced in this PR?

Make linkedin audience destination available for all the workspaces.

What is the related Linear task?

Resolves INT-XXX

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new checks got introduced or modified in test suites. Please explain the changes.

N/A

---

Developer checklist

• My code follows the style guidelines of this project

• No breaking changes are being introduced.

• All related docs linked with the PR?

• All changes manually tested?

• Any documentation changes needed with this change?

• I have executed schemaGenerator tests and updated schema if needed

• Are sensitive fields marked as secret in definition config?

• My test cases and placeholders use only masked/sample values for sensitive fields

• Is the PR limited to 10 file changes & one task?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

Summary by CodeRabbit

• Configuration Update
  • Simplified LinkedIn Audience destination configuration by updating the "hidden" property to a direct boolean value
  • Removed nested feature flag structure for visibility settings

[coderabbitai]

Walkthrough

The pull request involves a configuration change for the LinkedIn Audience destination. The modification simplifies the "hidden" property in the database configuration file, transforming it from a complex object with feature flag details to a straightforward boolean value of false. This change represents a streamlining of the configuration representation for the LinkedIn Audience destination.

Changes

File	Change Summary
src/configurations/destinations/linkedin_audience/db-config.json	Simplified "hidden" property from nested object to direct boolean false

Poem

🐰 A config tweak, so neat and light,
LinkedIn's hidden flag now shines bright
From complex object to simple state
A rabbit's config update - how great!
Boolean false, no flags in sight 🔧

---

📜 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 2318a6f and 4d9612a.

📒 Files selected for processing (1)

• src/configurations/destinations/linkedin_audience/db-config.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (1)

src/configurations/destinations/linkedin_audience/db-config.json (1)

34-34: LGTM! The change aligns with making the destination publicly available.

The simplification of the hidden flag from a feature flag object to false effectively makes the LinkedIn Audience destination available for all workspaces while maintaining the beta status.

Let's verify if the feature flag is used elsewhere in the codebase:

✅ Verification successful

Verified: The feature flag removal is safe and follows standard patterns

The change aligns with how destination visibility is controlled across the platform, and there are no code-level dependencies on the feature flag. The modification maintains consistency with other destination configurations that use the hidden flag.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the removed feature flag is referenced elsewhere
# Expected: No other references to ensure clean removal

# Search for the feature flag name
rg -i "AMP_linkedin_audience"

# Search for any LinkedIn Audience related feature flags
rg -i "linkedin.*audience.*feature"

Length of output: 67

---

Script:

#!/bin/bash
# Broader search for LinkedIn Audience references and feature flags

# Search for LinkedIn Audience references
rg -i "linkedin.*audience" -g "!*.json"

# Check other destination configurations for hidden flags
fd -e json -p "destinations" --exec grep -l "hidden" {}

# Look for feature flag related code
rg -i "feature.*flag" -g "!*.{json,md}"

Length of output: 1564

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (2318a6f) to head (4d9612a).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff            @@
##           develop     #1871   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           53        53           
  Branches         7         7           
=========================================
  Hits            53        53           

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