Skip to content

fixed typo in developer-docs #1993

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

Merged
merged 11 commits into from
Feb 22, 2023
Merged

fixed typo in developer-docs #1993

merged 11 commits into from
Feb 22, 2023

Conversation

ktsrivastava29
Copy link
Contributor

@ktsrivastava29 ktsrivastava29 commented Jan 27, 2022

Fixes #issue-number

I have verified that this pull request:

  • has no linting errors (npm run lint)
  • is from a uniquely-named feature branch and has been rebased on top of the latest develop branch. (If I was asked to make more changes, I have made sure to rebase onto develop then too)
  • is descriptively named and links to an issue number, i.e. Fixes #123

@welcome
Copy link

welcome bot commented Jan 27, 2022

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already.

@release-com
Copy link

release-com bot commented Jan 27, 2022

Release Environments

This pull request environment is provided by Release, learn more!
To see the status of the environment click on Environment Status below.

🔧Environment Status : https://app.releasehub.com/public/Processing%20Foundation/env-bccf9ff72b

@ktsrivastava29
Copy link
Contributor Author

Many of the .md files in the developer documents folder had punctuation and grammatical errors, which I've fixed. Please review the changes; if any modification is required, I'll be pleased to make them.

Copy link
Collaborator

@raclim raclim left a comment

Choose a reason for hiding this comment

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

Overall these changes look great, thanks for catching these! I added a few comments, but let me know what you think! :)

@@ -87,7 +87,7 @@ Structure your commit message like this:

- For common and reusable styles, write OOSCSS (Object-Oriented SCSS) with placeholders and mixins. For organizing styles, follow the [7-1 Pattern](https://sass-guidelin.es/#the-7-1-pattern) for Sass.

- We're using [ES6](http://es6-features.org/) and transpiling to ES5 using [Babel](https://babeljs.io/).
- We're using [ES6](http://es6-features.org/) and transpile to ES5 using [Babel](https://babeljs.io/).
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think 'transpiling' makes sense here, but could also see this sentence as a whole being rephrased as well!

@@ -1,12 +1,12 @@
# Proposed Public API extensions

This describes proposed extensions to the Public API. None of these extensions are confirmed, but are recorded here for reference and discussion.
This describes proposed extensions to the Public API. None of these extensions is confirmed but is recorded here for reference and discussion.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the verb "are" is referring to "extensions". Since "extensions" is plural, I think "are" could be kept!

@@ -485,14 +485,14 @@ afterEach(() => server.resetHandlers());
afterAll(() => server.close());
```

If the component makes use of the `formatDate` util, some of the functions in that rely on the `client/i18n.js` file that also makes an AJAX request, which sometimes leads to an `ERRCONNECTED` error on the console, even though your tests pass. You can fix it by adding a mock for that specific i18n file:
If the component makes use of the `formatDate` util, some of the functions in that rely on the `client/i18n.js` file also make an AJAX request, which sometimes leads to an `ERRCONNECTED` error on the console, even though your tests pass. You can fix it by adding a mock for that specific i18n file:
Copy link
Collaborator

Choose a reason for hiding this comment

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

I interpreted the updated phrasing to state that the functions themselves are also making an AJAX request, as opposed to the original docs, which I think implies that the client/i8n.js file is making AJAX requests in tandem with the functions.

However, I'm not entirely certain and feel that this entire sentence could possibly be made clearer, let me know what you think!

@@ -53,7 +53,7 @@ export function languageKeyToDateLocale(lang) {

## Translations

* Every component should introduce its own subset of keys inside a dictionary named after the component.
* Every component should introduce its subset of keys inside a dictionary named after the component.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think the "own" here helps provide emphasis, but could also be replaced with a different word!

@raclim raclim merged commit 362c486 into processing:develop Feb 22, 2023
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