yujunjun/strapi
1
0
Fork 0
mirror of https://github.com/strapi/strapi.git synced 2025-08-23 16:19:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix some spelling errors and standardiZe regional usages

Browse Source
This commit is contained in:
Ben Irvin 2023-07-28 11:12:04 +02:00
parent 8aa758396e
commit b5d94c2ff2
9 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
api-tests/core/admin/ee/review-workflows-content-types.test.api.js
View File

@ -262,7 +262,7 @@ describeOnCondition(edition === 'EE')('Review workflows - Content Types', () =>
});
test('It should steal content types from other workflows', async () => {
// There could be concurrency issues, so assert all workflows are transfered
// There could be concurrency issues, so assert all workflows are transferred
const res = await updateWorkflow(workflow2.id, {
contentTypes: [productUID, articleUID],
});

2
docs/docs/docs/00-intro.md
View File

@ -17,4 +17,4 @@ plugins/
├─ i18n/
```
This helps keep the documentation organised according to the file structure of the `packages` folder within the monorepo. From there however, is dependant on the documentation written, it will most likely change over time when the documentation grows and develops.
This helps keep the documentation organized according to the file structure of the `packages` folder within the monorepo. From there however, is dependant on the documentation written, it will most likely change over time when the documentation grows and develops.

2
docs/docs/docs/01-core/admin/02-permissions/01-how-they-work.mdx
View File

@ -142,7 +142,7 @@ The permissions are modified in the admin panel (on the [edit page](http://local
| -------------- | -------------------------------------------------------------------------------------------------------------------------- | ------ | -------- | ------------------------------------------------------------- |
| **action** | Id of the action that will be permitted. | string | required | `'plugin::content-manager.explorer.update'` |
| **subject** | Id of the subject on which the action will be permitted. | string | - | `'api::article.article'` |
| **properties** | List of the properties of the subject on wich the action will be permitted | object | - | `{ fields: ['title', 'description'], locales: ['en', 'fr'] }` |
| **properties** | List of the properties of the subject on which the action will be permitted | object | - | `{ fields: ['title', 'description'], locales: ['en', 'fr'] }` |
| **conditions** | List of the conditions that will be ran against an entry to determine whether the action on this entry is permitted or not | array | - | `['admin::is-creator']` |
A permission contains all needed information for the backend and the frontend to prevent users to perform non-permitted action.

2
packages/core/admin/admin/src/content-manager/components/EditViewDataManagerProvider/utils/cleanData.js
View File

@ -91,7 +91,7 @@ const cleanData = ({ browserState, serverState }, currentSchema, componentsSchem
/**
* Because of how repeatable components work when you dig into them the server
* will have no object to compare too therefore no relation array will be setup
* because the component has not been initialised, therefore we can safely assume
* because the component has not been initialized, therefore we can safely assume
* it needs to be added and provide a default empty array.
*/
let actualOldValue = get(rootServerState, trueInitialDataPath, []);

2
packages/core/admin/admin/src/content-manager/components/RelationInput/RelationInput.js
View File

@ -373,7 +373,7 @@ RelationInput.propTypes = {
};
/**
* This is in a seperate component to enforce passing all the props the component requires to react-window
* This is in a separate component to enforce passing all the props the component requires to react-window
* to ensure drag & drop correctly works.
*/
const ListItem = ({ data, index, style }) => {

4
packages/core/admin/admin/src/content-manager/hooks/useLazyComponents/tests/useLazyComponents.test.js
View File

@ -49,7 +49,7 @@ describe('useLazyComponents', () => {
expect(result.current.lazyComponentStore['plugin::test.test']).toBeDefined();
});
test('assuming the store has been initialised before hand, other hooks called should be able to access the global cache', async () => {
test('assuming the store has been initialized before hand, other hooks called should be able to access the global cache', async () => {
const { result: initialResult } = renderHook(() => useLazyComponents(['plugin::test.test']));
await waitFor(() =>
@ -72,7 +72,7 @@ describe('useLazyComponents', () => {
expect(result.current.lazyComponentStore).toEqual({});
});
test('assuming the store has been initialised before hand, other hooks called should be able to modify the global cache and access it', async () => {
test('assuming the store has been initialized before hand, other hooks called should be able to modify the global cache and access it', async () => {
const { result: initialResult } = renderHook(() => useLazyComponents(['plugin::test.color']));
await waitFor(() =>

2
packages/core/admin/admin/src/content-manager/sharedReducers/crudReducer/reducer.js
View File

@ -4,7 +4,7 @@ import produce from 'immer';
// NOTE: instead of creating a shared reducer here, we could also create a hook
// that returns the dispatch and the state, however it will mess with the linter
// and force us to either disable the linter for the hooks dependencies array rule or
// require us to add the dispatch to the array wich is not wanted. This refacto does not require us to
// require us to add the dispatch to the array which is not wanted. This refacto does not require us to
// to do any of this.
import {
CLEAR_SET_MODIFIED_DATA_ONLY,

2
packages/core/content-type-builder/admin/src/components/FormModal/index.js
View File

@ -690,7 +690,7 @@ const FormModal = () => {
onCloseModal();
}
// We don't need to end the loop here we want the reducer to be reinitialised
// We don't need to end the loop here we want the reducer to be reinitialized
// Logic for creating a component without clicking on the link in
// the left menu

2
packages/plugins/users-permissions/documentation/content-api.yaml
View File

@ -93,7 +93,7 @@ paths:
required: true
responses:
200:
description: Successfull registration
description: Successful registration
content:
application/json:
schema: