Skip to content

Conversation

@DeekshaVarshney123
Copy link

Hii @stevepiercy ,

I’ve attempted to fix issue #3092 by adding JavaScript and NodeJS to the Plone Vale accept vocabulary to ensure consistent spelling in the documentation.

Please review and let me know if any changes are required.
Thank you!

@DeekshaVarshney123
Copy link
Author

Thanks for the clarification.

I verified the official spelling on the Node.js website and updated the accepted vocabulary accordingly, keeping the list alphabetically sorted.

I also corrected a small number of obvious misspellings of the correct form in the documentation, avoiding code blocks and commands.

@stevepiercy
Copy link
Collaborator

@DeekshaVarshney123 OK, next push your changes to this PR. I see none of which you speak.

@DeekshaVarshney123
Copy link
Author

Hi @stevepiercy,

I have updated the spelling to 'Node.js' globally across all documentation files, changelogs, and storybook stories as requested. I have also sorted the vocabulary alphabetically in accept.txt and verified that all CI checks (including Vale) are now passing.

Please check if these changes are correct. If everything looks good for Node.js, I will proceed with fixing the 'JavaScript' misspellings in the next step.

Thank you!

Copy link
Collaborator

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

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

All of the 17 items in packages/**/news/ should not appear in this pull request. Only the one that you need to create for this PR should appear. I'm not sure what you did with git or how to resolve this part.

I noticed also that developers misnamed Node.js as either "node" or "Node" in numerous places in the docs, especially the change log. To fix that, please add (?i)node to the reject.txt file and replace them as needed. Note that it's possible that the word "node" is used per the English dictionary definition, in which case those instances should remain as "node". Keep in mind we want to correct the spelling of the product "Node.js" only.

@DeekshaVarshney123
Copy link
Author

Hi @stevepiercy,

I've updated the PR. I accidentally included the correct spelling in the reject.txt earlier, but I've fixed it now to only reject NodeJS and (?i)node. I also rebased the branch to clear out the extra news items and updated 'Node' to 'Node.js' where it refers to the product.

Regarding the failing Acceptance Test (24.x), could you please check if it's related to my changes or if it's a flaky test?
Thank you!

Copy link
Collaborator

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

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

Almost all of the changes look good, except for a couple. Please see my comments for details. Thank you!

@stevepiercy
Copy link
Collaborator

@DeekshaVarshney123 take a look at the output from running make vale:

Compare it to the line that the error references:

I think the issue is that the period in Node.js in styles/config/vocabularies/Plone/accept.txt is interpreted as a regular expression, meaning any single character. There's also problems in reject.txt.

Try changing the value in accept.txt to:

Node\.js

And in reject.txt to these lines:

(?i)node\s
node\.
(?i)NodeJS

then run make docs-vale again to see if that reduces the errors significantly?

@DeekshaVarshney123
Copy link
Author

Hi @stevepiercy,

thanks for the review. I have updated the files as requested:
Reverts: Changed back to node in the upgrade and add-on guides.
Vocab: Updated accept.txt to Node.js and reject.txt with your regex suggestions.
News Item: Added my handle for credit.

I ran make docs-vale and Node-related errors like "Avoid using Node." still persist. It seems the escaped dot in accept.txt isn't fully resolving the issue in all files. Please let me know how to proceed.

@stevepiercy
Copy link
Collaborator

@DeekshaVarshney123 I'm sorry, but I can't spare time to give you explicit instructions for how to resolve the issues. At that point, I'd be doing the work myself, and you wouldn't get credit.

Configuring Vale is tricky, and requires repeated testing until the regular expressions are exactly right. It's especially tricky because we don't want false positives or negatives in the results. I hope that my first attempt to resolve the issues leads you to discover a better resolution.

The best direction I can give you is the following.

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