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

add descripiton and keywords to package.json #108

Merged
merged 1 commit into from
Jun 29, 2022

Conversation

juliannzhou
Copy link
Contributor

This PR adds description and keywords to package.json. The description is copied from README and keywords provided by product.

J=SLAP-2190
TEST=manual

@juliannzhou juliannzhou requested a review from a team as a code owner June 29, 2022 20:35
@juliannzhou juliannzhou changed the title add descripiton and keywords to package.json. add descripiton and keywords to package.json Jun 29, 2022
@coveralls
Copy link

Coverage Status

Coverage remained the same at 92.704% when pulling 0a9e9f4 on dev/description_and_keywords into f9d7aa9 on main.

"answers",
"yext",
"react",
"components"
Copy link
Contributor

Choose a reason for hiding this comment

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

Did product ask for "components" and "react" here? This library doesn't have any components in it, and also doesn't use react

Copy link
Contributor

Choose a reason for hiding this comment

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

I would probably put "redux" here if anything

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Product only gave me one list, but none of the repositories have keywords in package.json. I thought I'd just put the same list, but I was wondering if we need different lists of keywords for all of the repositories?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I merged this into main by mistake, but I've reverted the changes.

Copy link
Contributor

@nmanu1 nmanu1 left a comment

Choose a reason for hiding this comment

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

can this PR be merged into develop instead of main

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.

None yet

4 participants