Skip to content

Commit

Permalink
feat: Update posts.md.
Browse files Browse the repository at this point in the history
  • Loading branch information
Starciad authored Apr 3, 2024
1 parent 6c5b8ee commit 5f22020
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions .github/docs/entities/posts.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,8 +47,8 @@ await client.Posts.GetPostsAsync(new R34PostsSearchBuilder());
await client.Posts.GetPostsAsync(new R34PostsSearchBuilder()
{
Limit = 1000,
Tags = new R34TagModel[] {
new R34TagModel("Bowser"),
Tags = new R34FormattedTag[] {
new R34FormattedTag("Bowser"),
},
});
```
Expand All @@ -73,8 +73,8 @@ In order to obtain information from each post, we can place the **Data** field i
R34Posts posts = await client.Posts.GetPostsAsync(new R34PostsSearchBuilder()
{
Limit = 1000,
Tags = new R34TagModel[] {
new R34TagModel("Bowser"),
Tags = new R34FormattedTag[] {
new R34FormattedTag("Bowser"),
},
});

Expand Down Expand Up @@ -108,8 +108,8 @@ for(int i = 0; i < 2; i++)
R34Posts posts1 = await client.Posts.GetPostsAsync(new R34PostsSearchBuilder()
{
Limit = 1000,
Tags = new R34TagModel[] {
new R34TagModel("Bowser"),
Tags = new R34FormattedTag[] {
new R34FormattedTag("Bowser"),
},

// Defines the offset to be searched.
Expand Down Expand Up @@ -141,8 +141,8 @@ See the example below, which downloads all posts made in one request:
R34Posts posts = await client.Posts.GetPostsAsync(new R34PostsSearchBuilder()
{
Limit = 10,
Tags = new R34TagModel[] {
new R34TagModel("Bowser"),
Tags = new R34FormattedTag[] {
new R34FormattedTag("Bowser"),
},
});

Expand All @@ -166,4 +166,4 @@ Additionally, it's advisable to implement some sort of progress monitoring featu
## `6.` BEST PRACTICES
### `1.` Save all information in a cache.

It is essential to emphasize that all methods that receive information and return collections make requests to the Rule34 API. In this context, it is highly recommended to store the obtained values in any form of cache of your preference. By doing so, we avoid redundant requests and the waste of memory resources with lists containing a large number of elements that are automatically created by the system.
It is essential to emphasize that all methods that receive information and return collections make requests to the Rule34 API. In this context, it is highly recommended to store the obtained values in any form of cache of your preference. By doing so, we avoid redundant requests and the waste of memory resources with lists containing a large number of elements that are automatically created by the system.

0 comments on commit 5f22020

Please sign in to comment.