Skip to content

Commit

Permalink
Fix some typos in docs
Browse files Browse the repository at this point in the history
  • Loading branch information
Klaas058 committed Jun 18, 2024
1 parent 9aa1ef1 commit 1c0f9b8
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/under-the-hood.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Each property of the DTO will be checked: does it have a PHP type and/or does it
A good example of a type processor is the `ReplaceDefaultsTypeProcessor`. This one will replace some default types you can define in the configuration with a TypeScript representation. For example transforming `DateTime` or `Carbon` types to `string`.

DTO's often have properties that contain other DTO's, or even other custom types. This is why we'll also keep track of the missing symbols when transforming a DTO.
Let's say your DTO has a property that contains another DTO. At the moment of transformation, the package will not know how that other DTO should be transformed. We'll temporarily use a missing symbol that can be replaced by a reference to the correcty DTO type later.
Let's say your DTO has a property that contains another DTO. At the moment of transformation, the package will not know how that other DTO should be transformed. We'll temporarily use a missing symbol that can be replaced by a reference to the correct DTO type later.

## Step 3: Replacing missing symbols

Expand Down
2 changes: 1 addition & 1 deletion docs/usage/annotations.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ It is possible to directly represent a type as TypeScript within your PHP code:
class CustomString{}
```

Now when `Language` is being transformed, the TypeScript respresentation is used:
Now when `Language` is being transformed, the TypeScript representation is used:

```tsx
export type CustomString = string | null;
Expand Down

0 comments on commit 1c0f9b8

Please sign in to comment.