Skip to content

📝 docs(arc 35): methods documentation #30

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

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

matdudek
Copy link

No description provided.

Copy link

linear bot commented Dec 14, 2023

Copy link

vercel bot commented Dec 14, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
repository-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 29, 2023 3:08pm

Copy link

Coverage Report for packages/repository

Status Category Percentage Covered / Total
🟢 Lines 97.97% / 80% 145 / 148
🟢 Statements 97.43% / 80% 152 / 156
🟢 Functions 95.45% / 80% 63 / 66
🟢 Branches 93.18% / 80% 82 / 88
File CoverageNo changed files found.
Generated in workflow #51

Comment on lines 24 to 25
`Methods<TSchema>`: This is a generic type called `Methods`. It takes a type parameter `TSchema`, which is expected to extend the `EntitySchema`.<br/>
This means that `Methods` is a reusable type where we can use it for different EntityType. (dunno if I should explain this @TODO)
Copy link
Contributor

Choose a reason for hiding this comment

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

Skup się najpierw na celu jaki realizuje dany typ - w tym przykładzie Methods stanowią strukturę dla deklaracji metod w modelu Entity.

Dopiero w kolejnej sekcji jak ten typ jest zbudowany - ale skupiając się tylko na najtrudniejszych kawałkach.

Copy link
Author

Choose a reason for hiding this comment

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

Wydaje się, że rozpykane to zostało 😄

@grixu grixu added the documentation Improvements or additions to documentation label Dec 22, 2023
@matdudek matdudek force-pushed the feature/arc-35-methods-documentation branch from 06ca3c0 to 6d3dcba Compare December 28, 2023 13:00
@matdudek matdudek force-pushed the feature/arc-35-methods-documentation branch from 6d3dcba to baaff3e Compare December 28, 2023 16:55
@matdudek matdudek changed the title draft: 📝 docs(arc 35): methods documentation 📝 docs(arc 35): methods documentation Dec 28, 2023
@matdudek matdudek force-pushed the feature/arc-35-methods-documentation branch from baaff3e to 0c69f78 Compare December 28, 2023 16:58
Comment on lines +48 to +55
It's an `object` with two keys.

```ts
export type PrototypeMethods<TSchema extends EntitySchema> = {
toObject(): TSchema
toJson(): string
}
```
Copy link
Contributor

Choose a reason for hiding this comment

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

Zrobiłem update po refactorach

```ts
export type Methods<TSchema extends EntitySchema> = Record<
string, // keys
(this: TSchema, ...args: any[]) => any // values
Copy link
Contributor

Choose a reason for hiding this comment

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

To jescze trzeba zupdate-ować

The calculations will be always an union (Type is running mechanism twice for `Methods<TSchema>` & `undefined`)
and result will contain `"true"` or `"false"` or `0`

#### 3. Augmentation of Methods
Copy link
Contributor

Choose a reason for hiding this comment

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

Prostszym pojęciem jest merge i to bym poszedł niż w Augmentation. ;)

@grixu
Copy link
Contributor

grixu commented Dec 29, 2023

Generalnie dobra robota 👍

Zrobiłem Ci update do maina, bo trochę konfliktów było, mi było je prościej rozwiązać ;)

@grixu
Copy link
Contributor

grixu commented Dec 29, 2023

Dodałem markdownlint w między czasie - więc dorzuć jeszcze poprawki i możemy zamykać ;)

@grixu
Copy link
Contributor

grixu commented Feb 9, 2024

@coderabbitai zrób proszę analizę tego pull requesta. Sprawdź również czemu nie przeszedł pipeline CI

Copy link

coderabbitai bot commented Feb 9, 2024

@grixu: Analiza pull requesta wykazała, że konfiguracja CI (ci.yml) zawiera krok markdownlint-cli2-action, który jest skonfigurowany do lintowania plików Markdown w katalogu docs. Prawdopodobnie niepowodzenie pipeline CI jest związane z problemami lintowania w tych plikach Markdown. Zalecam sprawdzenie logów CI, aby znaleźć szczegóły dotyczące problemów z lintowaniem i dokonanie odpowiednich poprawek w plikach Markdown w katalogu docs, aby zapewnić pomyślne przejście pipeline CI.

Analysis chain


Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Find CI configuration files (e.g., GitHub Actions, GitLab CI, etc.)
fd '\.github/workflows|\.gitlab-ci\.yml$'

# List the most recent commits to see if any might have affected the CI pipeline
git log -n 5 --pretty=format:"%h - %s"

Length of output: 362



Script:

#!/bin/bash
# Assuming there might be multiple CI configuration files, read the contents of all files in the .github/workflows directory
fd '\.github/workflows' --exec cat {}

Length of output: 41



Script:

#!/bin/bash
# List CI configuration files in the .github/workflows directory
fd '.yml$' '.github/workflows'

# Assuming the list command works, the next step would be to read each file. However, this script will first ensure we can list the files correctly.

Length of output: 80



Script:

#!/bin/bash
# Read the contents of the CI configuration file to understand the CI pipeline setup, especially regarding markdownlint
cat .github/workflows/ci.yml

Length of output: 1317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants