Skip to content

feat: x-linkedin extension support#1155

Open
catosaurusrex2003 wants to merge 4 commits intoasyncapi:masterfrom
catosaurusrex2003:linkedin-extension
Open

feat: x-linkedin extension support#1155
catosaurusrex2003 wants to merge 4 commits intoasyncapi:masterfrom
catosaurusrex2003:linkedin-extension

Conversation

@catosaurusrex2003
Copy link
Contributor

Description

support for x-linkedin extension: https://github.com/asyncapi/extensions-catalog/blob/master/extensions/linkedin.md

just like how this was implemented #994

Related issue(s)
None

@sonarqubecloud
Copy link

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Sep 12, 2025
@catosaurusrex2003
Copy link
Contributor Author

still relevant

@github-actions github-actions bot removed the stale label Sep 18, 2025
@sonarqubecloud
Copy link

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.

There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jan 17, 2026
"build:types": "tsc -p tsconfig.types.json",
"build:styles": "npm run build:styles:dev && npm run build:styles:prod",
"build:styles:dev": "cross-env NODE_ENV=production postcss src/styles/default.css -o styles/default.css --verbose",
"build:styles:dev": "cross-env NODE_ENV=development postcss src/styles/default.css -o styles/default.css --verbose & cross-env NODE_ENV=development postcss src/styles/default.css -o styles/default.min.css --verbose",
Copy link
Member

Choose a reason for hiding this comment

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

@catosaurusrex2003 remind me again why we are doing this?

Copy link
Contributor Author

@catosaurusrex2003 catosaurusrex2003 Feb 15, 2026

Choose a reason for hiding this comment

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

To prevent tree-shaking.

Making the NODE_ENV as development bundles styles which we are not even using in the project.

This enables us to use (never used before) classnames in development, without needing to build the styles again and again.

Copy link
Member

@AceTheCreator AceTheCreator left a comment

Choose a reason for hiding this comment

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

Left you some review @catosaurusrex2003

parent={item}
/>
);
} else return null;
Copy link
Member

Choose a reason for hiding this comment

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

@catosaurusrex2003 I'm curious about the approach here, what's the advantage of returning null instead of using an else statement? Why is handling it in a single iteration better than separating the logic as you did in this PR?

@github-actions github-actions bot removed the stale label Jan 23, 2026
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants