Skip to content

Fix messages #153

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Fix messages #153

wants to merge 2 commits into from

Conversation

kenamverma
Copy link
Contributor

No description provided.

@@ -1,5 +1,6 @@
import { findAttr, isAttributesEmpty } from "./utils/node";
import metadata from '@salesforce-ux/sds-metadata';
import { formatMessageWithSuggestions } from '../../../shared-utils/src';
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should we use as a package or relative path?

Copy link
Contributor

Choose a reason for hiding this comment

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

  • Letz create package , but skipped from publishing
  • move all rule message formatting related code into this
  • update esling and stylelint plugins to use this package
  • update esbuild of esling and stylelint plugins to bundle this package

Name of the package can be rule-meta

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Planning to hold this PR until we decide on the rule-meta end. I can create the function on top of that work. Don't want to merge two work items in this PR.

* @param suggestions Array of suggestion objects to include
* @returns Stringified JSON object containing message and suggestions
*/
export function formatMessageWithSuggestions(message: string, suggestions: string[]): string {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Created a function so that we can in case needed.

@sf-nithappu sf-nithappu added the under review PR review is active and in progress label May 8, 2025
@sf-nithappu sf-nithappu marked this pull request as draft May 12, 2025 17:59
@sf-nithappu
Copy link
Contributor

Planning to hold this PR until we decide on the rule-meta end. I can create the function on top of that work. Don't want to merge two work items in this PR.

@sf-nithappu sf-nithappu added on-hold PR is on hold. No review or updates are expected and removed under review PR review is active and in progress labels May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on-hold PR is on hold. No review or updates are expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants