feat(ct): angular component testing #27783

sand4rt · 2023-10-24T20:33:39Z

closes: #14153 and https://github.com/sand4rt/playwright-ct-angular

TODO

pavelfeldman · 2023-10-25T17:17:22Z

What's out plan here, is it ready to land? Is it based on Younes's work or is this something different?

yjaaidi

Great job @sand4rt!
Here are a couple of things that would be nice to solve before merging.
Let me know if you want me to contribute to your branch directly with some PRs.

The main discussion here is about vite plugin replacement and configuration.

packages/playwright-ct-angular/registerSource.mjs

packages/playwright-ct-angular/index.js

packages/playwright-ct-angular/package.json

yjaaidi · 2023-10-25T21:42:12Z

What's out plan here, is it ready to land?

Hey @pavelfeldman! I just shared my feedback with @sand4rt.
Once we agree on that and fix what can be fixed, the PR should be ready.

Is it based on Younes's work or is this something different?

It doesn't matter anymore. There was just a misunderstanding.
We were just a bit disappointed for not merging efforts but now we are working together to provide what the community is waiting for and that's what matters.

sand4rt · 2023-10-27T10:03:15Z

Hey guys, thanks for the comments! I'm AFK for a couple of days. Will hopefully look at the PR by the end of next week as well

edbzn

The added logo is the Angular.js one, here's the link to the correct Angular logo.

packages/playwright-ct-angular/index.js

sand4rt · 2023-11-05T20:19:38Z

The added logo is the Angular.js one, here's the link to the correct Angular logo.

Hi @edbzn, thanks for the input! Would you like to make the change by creating a PR against this branch? See #27783 (comment) for more details

edit: Angular just released their new logo: https://angular.dev/press-kit

yjaaidi · 2023-11-13T22:59:43Z

I just noticed that the tests themselves are using Angular 15.
Should we create a different folder for Angular 16 & Angular 17 and that would require lots of duplication?
Or should we do something at the test-all.spec.js level but that would be a bit too magical?
Or should the "experimental" CT only handle the last version of the framework?
cc. @mxschmitt @pavelfeldman @sand4rt

tests/components/ct-angular/src/assets/logo.svg

yjaaidi · 2023-11-21T16:40:20Z

Hey @sand4rt, I just created a create-playwright PR microsoft/create-playwright#106 to move the Angular vite plugin config to "user-land".

This way, we can update the todo list as this:

Do not handle routing and let users use router testing harness
Update tests to use Angular 17
Update the documentation
Remove @analogjs/vite-plugin-angular dependency & setup.
Update https://github.com/microsoft/create-playwright to generate playwright config with @analogjs/vite-plugin-angular and add it to project dependencies.

Here are the advantages of moving the Angular vite plugin setup to the create-playwright generator:

@analogjs/vite-plugin-angular has to catch up with Angular internals to make it work for future versions. Currently, the Angular internals it relies on can break at any Angular minor or patch version. Meaning that @playwright/experimental-ct-angular will have to catch up to by updating the dependency which also means a new Playwright release.
Users can easily choose the @analogjs/vite-plugin-angular version of their choice.
Users can easily choose the @analogjs/vite-plugin-angular configuration of their choice.
Users can easily choose another plugin.
This doesn't add any dependency to this workspace.

The drawbacks are:

It doesn't work out of the box if users don't use the generator or if they use the package manually without reading the docs.
Users will have to manually keep @analogjs/vite-plugin-angular up-to-date.

Of course, this is just a temporary solution until the Angular team releases an official vite plugin which will at least warranty major version compatibility.

yjaaidi · 2024-02-15T07:30:12Z

Hey @sand4rt are you available in the upcoming days or weeks so we can finish this 😊
Maybe if you could just update your branch I could send you a PR.
Thanks!

flobacher · 2024-02-15T09:58:16Z

Great news @yjaaidi and @sand4rt! Thank you so much for your effort time and persistence!!!

sand4rt · 2024-02-22T19:12:05Z

Maybe if you could just update your branch I could send you a PR.

Hey @yjaaidi, #29544 needs to be resolved before i can update. I could resolve the merge conflicts later on if needed, so don't let that hold you back.

For the people willing to contribute; beta testing would also help a lot to ensure everything operates as expected, your feedback is very welcome!

yjaaidi · 2024-02-23T15:31:03Z

Thanks @sand4rt!
@edbzn and I had to update and fix #29544 before moving forward.

I think that we have everything now 😊:

✨ it works with thew new transformation
✨ template rendering (thanks to the new transformation system, amazing job @pavelfeldman)
✨ signal inputs support
✨ moved out analog vite plugin from the package
✨ Angular 17 support
✨ and passing providers

Cf. sand4rt#5

maartentibau · 2024-02-27T17:44:50Z

Great great great work! Thank you!!
At this moment this will only support standalone components right?

zargham-leanix · 2024-03-20T10:36:59Z

Great work @sand4rt @yjaaidi
When this PR is expected to be merged ?

sand4rt · 2024-05-10T14:31:33Z

Hey @pavelfeldman, the PR is finally set for review by the Playwright team! We have deliberately kept the adapter minimal for now and postponed the documentation until more people have tested it and shared their feedback. We would like to gradually make improvements here and there after the merge.

rainerhahnekamp · 2024-05-11T10:25:08Z

Congratulations to all of you. That's a milestone in Angular testing history!

Just a small remark: From what I've seen, there is no possibility to provide services, right?

If that's the case, it would be great to add this as the next feature once this branch is merged.

As you know, the vast majority of Angular Components usually depend on Services. If we could mock these services, the number of people who could test on a large scale would increase "exponentially."

Either way, congratulations and a thousand thanks again. I'm looking forward to it

sand4rt · 2024-05-11T10:54:46Z

Congratulations to all of you. That's a milestone in Angular testing history!

Just a small remark: From what I've seen, there is no possibility to provide services, right?

If that's the case, it would be great to add this as the next feature once this branch is merged.

As you know, the vast majority of Angular Components usually depend on Services. If we could mock these services, the number of people who could test on a large scale would increase "exponentially."

Either way, congratulations and a thousand thanks again. I'm looking forward to it

Providers/imports are still open for discussion indeed. We've decided to merge the library first before continuing the discussion: sand4rt#5 (comment)

I think it could either be supported like the other frameworks through the hooksConfig:

// playwright/index.ts
beforeMount(async ({ TestBed, hooksConfig }) => {
  TestBed.configureTestingModule({
    imports: hooksConfig?.imports,
    providers: hooksConfig?.providers
  });
});

test('hooks config', async ({ mount }) => {
  const component = await mount(AngularComponent, {
    hooksConfig: {
      imports: [Component],
      providers: [Service],
    }
  });
  await expect(component).toContainText('boop');
});

or with dedicated APIs:

test('imports and providers', async ({ mount }) => {
  const component = await mount(AngularComponent, {
    imports: [Component],
    providers: [Service],
  });
  await expect(component).toContainText('boop');
});

rainerhahnekamp · 2024-05-11T15:29:23Z

Understood, then let's wait for the merge and then continue the discussion. Congrats again.

maartentibau · 2024-05-12T12:11:03Z

Amazing work @sand4rt @yjaaidi ... this really is a milestone.
Can't thank you guys enough for this effort! 👏 👏 👏

chronospatian · 2024-05-13T01:12:03Z

@yjaaidi I am running into some issues while testing this library.
~~sand4rt/playwright-ct-angular#50~~ Resolved
~~sand4rt/playwright-ct-angular#51~~ Resolved
~~sand4rt/playwright-ct-angular#52~~ Resolved

~~I have pulled and linked the PR branch and still face these errors.~~ I also cannot import from @angular/material without adding "type": "module" to my package.json, or changing all my files to .mts.

Other than that it's working great so far. Thanks so much for this.

yjaaidi · 2024-05-13T08:09:16Z

@yjaaidi I am running into some issues while testing this library. sand4rt/playwright-ct-angular#50 ~~sand4rt/playwright-ct-angular#51~~ Resolved ~~sand4rt/playwright-ct-angular#52~~ Resolved

I have pulled and linked the PR branch and still face these errors. I also cannot import from @angular/material without adding "type": "module" to my package.json, or changing all my files to .mts.

Other than that it's working great so far. Thanks so much for this.

Hi @chronospatian, what is the value of ctViteConfig in the playwright config file?
Did you try this:

    ctViteConfig: {
      plugins: [analog()], // or [swc.vite(swcAngularUnpluginOptions())]
      resolve: {
        /* @angular/material is using "style" as a Custom Conditional export to expose prebuilt styles etc... */
        conditions: ['style'],
      },
    },

yjaaidi · 2024-05-13T08:22:57Z

@rainerhahnekamp note that there are some known limitations on what can be used in providers.
We've documented this here https://github.com/jscutlery/devkit/tree/main/packages/playwright-ct-angular#%EF%B8%8F-known-limitations but we will add this to playwright docs once this is merged.

chronospatian · 2024-05-13T08:35:37Z

@yjaaidi I am using the same config as you have it here: https://github.com/sand4rt/playwright/blob/hello-angular-ct/tests/components/ct-angular/playwright.config.mts

~~Except I also added globalThis.window = globalThis to work around window being undefined when using the beforeMount hook.~~

chronospatian · 2024-05-13T08:40:02Z

~~Actually it doesn't appear that the beforeMount hook is being called at all... Not sure what I'm doing wrong.~~ I was putting beforeMount in the wrong file, apologies.

sand4rt · 2024-05-13T11:19:38Z

@chronospatain you might want to check out #23662 for the esm/cjs issues

chronospatian · 2024-05-13T11:32:12Z

The last thing I did to get hooks working was to make sure playwright/index.ts was included in the tsconfig files referenced by the vite plugin.

yjaaidi · 2024-05-13T15:38:12Z

I was putting beforeMount in the wrong file, apologies.

In which file did you put it initially?
I'm curious about common mistakes/problems. 😉

chronospatian · 2024-05-13T23:57:45Z

@yjaaidi I initially put it in the spec file, like beforeEach.

chronospatian · 2024-05-14T09:39:37Z

Are there plans to add support for testing Directives and Pipes?

eg.

await mount(`<div [myDirective]="value | myPipe"></div>`, {
  imports: [MyDirective, MyPipe],
  props: {
    value: "abc"
  }
})

dgozman · 2024-05-14T18:09:35Z

packages/playwright-ct-angular/package.json

+ "typescript": "~5.2.0",
+ "zone.js": "~0.14.0"
+ },
+ "peerDependencies": {


This seems to be the first time we declare peerDependencies, and we don't really like them. Where do we use them? Can we avoid declaring them as peers? Should we hard-depend on them, similar to depending on vite-plugin-solid in @playwright/experimental-ct-solid?

dgozman · 2024-05-14T18:10:43Z

packages/playwright-ct-angular/index.d.ts

+export type ComponentEvents = Record<string, Function>;
+
+export interface MountOptions<HooksConfig extends JsonObject, Component> {
+ props?: Partial<Component> | Record<string, unknown>, // TODO: filter props and handle signals


Could you expand a bit on the TODO?

The types are quite loose now while they should be stricter. @yjaaidi you already made something for this right?

dgozman · 2024-05-14T18:13:02Z

packages/playwright-ct-angular/registerSource.mjs

+
+/** @typedef {import('../playwright-ct-core/types/component').ObjectComponent} ObjectComponent */
+
+import 'zone.js';


Why do we need this one?

dgozman · 2024-05-14T18:16:29Z

packages/playwright-ct-core/src/tsxTransform.ts

+ traverse(node, {
+ enter: p => {
+ // Treat calls to mount and all identifiers in arguments as component usages.
+ // e.g. mount(MyComponent, { imports: [OtherComponent], providers: [Token]})


So far, we like the idea of not depending on the usage, but only on declaration. It seems like Angular has a nice practice of putting components into Button.component.ts files, so perhaps we can use this convention and treat .component as a component file similar to .vue and .svelte?

Solely relying on the file extension might not be a good idea because of:

Support for imports/providers in Angular is a must have (see this for more info)

Native web components don't have a common file extension: (see this for more info)

Vue components are not always defined in a .vue file (see this for more info)

Hmm... Could you elaborate on the imports/providers bit? I followed the link, and it seems to import AngularComponent, presumably from the AngularComponent.component file?

I also think that vue and lit are a different story, so I'd rather not mix them up in this PR aiming to support angular. We can have a separate discussion with pros and cons about it in #30269.

dgozman · 2024-05-14T18:17:47Z

tests/components/ct-angular/.gitignore

@@ -0,0 +1,45 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+


This is an impressive gitignore file! Was it generated by angular cli for you?

Yeah, tests/components/ct-angular was generated by angular cli

tests/components/ct-angular/src/assets/logo.svg

tests/components/ct-angular/src/components/button.component.html

dgozman · 2024-05-14T20:43:47Z

packages/playwright-ct-angular/registerSource.mjs

+ for (const hook of window.__pw_hooks_after_mount || [])
+ await hook({ hooksConfig });
+
+ __pwFixtureRegistry.set(rootElement.id, fixture);


Why mapping from id, and not from the rootElement itself?

dgozman · 2024-05-14T20:46:55Z

packages/playwright-ct-angular/registerSource.mjs

+} from '@angular/platform-browser-dynamic/testing';
+
+/** @type {WeakMap<import('@angular/core/testing').ComponentFixture, Record<string, import('rxjs').Subscription>>} */
+const __pwOutputSubscriptionRegistry = new WeakMap();


Instead of a WeakMap, we usually use a symbol. However, in this case it seems like we can combine this map with __pwFixtureRegistry?

// rootElement -> fixture, subscriptions Map<Element, { fixture: import('@angular/core/testing').ComponentFixture, subscriptions: Record<string, import('rxjs').Subscription> }>

dgozman · 2024-05-14T20:49:24Z

packages/playwright-ct-angular/registerSource.mjs

+ throw new Error('Only standalone components are supported');
+
+ TestBed.configureTestingModule({
+ imports: [component.type],


If we aim to support components as parameters (for slots?), do we have to list all component types in this imports list?

chronospatian · 2024-05-15T05:01:54Z

The test fixture appears to be anchored to the wrong element. This causes some getters, matchers and locators to fail or behave unexpectedly.

import { Component, ElementRef} from '@angular/core';

@Component({
  standalone: true,
  template: `<div>Test</div>`,
})
export class AttributeComponent {
  constructor(element: ElementRef) {
    element.nativeElement.setAttribute('name', 'hello')
  }
}

import { AttributeComponent } from '@/components/attribute.component';
import { expect, test } from '@playwright/experimental-ct-angular';
import type { HooksConfig } from 'playwright';

test('has name attribute', async ({ mount }) => {
  const component = await mount<HooksConfig>(AttributeComponent);
  // works
  await expect(component.page().locator('#root').getAttribute('name')).resolves.toBe('hello');
  // doesn't work
  await expect(component.getAttribute('name')).resolves.toBe('hello');

  // works
  await expect(component.page().locator('#root')).toHaveAttribute('name', 'hello');
  // doesn't work
  await expect(component).toHaveAttribute('name', 'hello');
});

chronospatian · 2024-05-15T06:11:27Z

packages/playwright-ct-angular/registerSource.mjs

+async function __pwRenderComponent(component) {
+ const componentMetadata = reflectComponentType(component.type);
+ if (!componentMetadata?.isStandalone)
+ throw new Error('Only standalone components are supported');
+
+ TestBed.configureTestingModule({
+ imports: [component.type],
+ });
+
+ await TestBed.compileComponents();
+
+ const fixture = TestBed.createComponent(component.type);
+ fixture.nativeElement.id = 'root';
+
+ __pwUpdateProps(fixture, component.props);
+ __pwUpdateEvents(fixture, component.on);
+
+ fixture.autoDetectChanges();
+
+ return fixture;
+}


TestBed.createComponent discards the root element, which causes the locator to break. Suggested refactor below should resolve this issue:

/** * @param {ObjectComponent & MountOptions} component * @param {HTMLElement} rootElement */ async function __pwRenderComponent(component, rootElement) { const componentMetadata = reflectComponentType(component.type); if (!componentMetadata?.isStandalone) throw new Error('Only standalone components are supported'); TestBed.configureTestingModule({ imports: [component.type], }); await TestBed.compileComponents(); const fixture = TestBed.createComponent(component.type) rootElement.replaceChildren(fixture.nativeElement) document.body.replaceChildren(rootElement) __pwUpdateProps(fixture, component.props); __pwUpdateEvents(fixture, component.on); fixture.autoDetectChanges(); return fixture; }

tests/components/ct-angular/playwright.config.mts

chronospatian

With the locator fix these tests should be updated.

tests/components/ct-angular/tests/events.spec.ts

tests/components/ct-angular/tests/update.spec.ts

chronospatian · 2024-05-15T12:21:21Z

@yjaaidi I've created a PR with fixes for the above and support for template strings sand4rt#6

github-actions · 2024-05-15T15:07:39Z

Test results for "tests 1"

1 flaky

⚠️ [firefox-page] › page/frame-goto.spec.ts:46:3 › should continue after client redirect

27343 passed, 662 skipped
✔️✔️✔️

Merge workflow run.

github-actions · 2024-05-16T07:41:41Z

Test results for "tests 1"

2 failed
❌ [playwright-test] › playwright.ct-react.spec.ts:253:5 › should pass "key" attribute from JSX in variable
❌ [installation tests] › playwright-electron-should-work.spec.ts:20:5 › electron should work

2 flaky

⚠️ [chromium-library] › library/capabilities.spec.ts:141:3 › should not crash on showDirectoryPicker
⚠️ [playwright-test] › ui-mode-test-screencast.spec.ts:21:5 › should show screenshots

27009 passed, 610 skipped
✔️✔️✔️

Merge workflow run.

packages/playwright-ct-angular/registerSource.mjs

chronospatian · 2024-05-24T00:09:22Z

I get errors when I try to import other values from a component file.

// @/components.counter.component
import { Component, EventEmitter, Input, Output } from '@angular/core';

// adding this line
export const count = 10

@Component({
   template: `{{count}}`
})
export class CounterComponent {
   count = count
}

import { test, expect } from '@playwright/experimental-ct-angular';
import { count, CounterComponent } from '@/components/counter.component';

test('should mount', async ({ mount }) => {
  const component = await mount(CounterComponent);

  await expect(component).toHaveText(`${count}`)
});

When I try to run this test I get the following error

SyntaxError: Cannot use import statement outside a module

   at ../src/components/counter.component.ts:1

> 1 | import { Component, EventEmitter, Input, Output } from '@angular/core';
    | ^
  2 |
  3 | @Component({
  4 |   standalone: true,

    at Object.<anonymous> (/Git/playwright/tests/components/ct-angular/src/components/counter.component.ts:1:1)
    at Object.<anonymous> (/Git/playwright/tests/components/ct-angular/tests/update.spec.ts:2:1)

Error: No tests found.
Make sure that arguments are regular expressions matching test files.
You may need to escape symbols like "$" or "*" and quote the arguments.

If I set "type: module" in package.json, then I get a different error.

Error: Standard Angular field decorators are not supported in JIT mode.

    at PropDecorator (/Git/playwright/tests/packages/core/src/util/decorators.ts:161:17)
    at applyDec (/Git/playwright/tests/components/ct-angular/src/components/counter.component.ts:3:1813)
    at/Git/playwright/tests/components/ct-angular/src/components/counter.component.ts:3:3514
    at _applyDecs (/Git/playwright/tests/components/ct-angular/src/components/counter.component.ts:3:3685)
    at /Git/playwright/tests/components/ct-angular/src/components/counter.component.ts:23:2

Lastly, if I change the test slightly:

export const count = { value: 10 }

I get yet another error:

SyntaxError: Identifier 'CounterComponent' has already been declared

This is very confusing! I guess this is a limitation of the playwright component test, so the solution here would be to extract the variable to another file that has no Angular imports or component usages, or to not import those values into the test to begin with and use hard coded values in the test.

sand4rt force-pushed the hello-angular-ct branch from aa9b3fe to 71599da Compare October 24, 2023 20:51

This comment has been minimized.

Sign in to view

yjaaidi reviewed Oct 25, 2023

View reviewed changes

edbzn reviewed Oct 29, 2023

View reviewed changes

packages/playwright-ct-angular/index.js Outdated Show resolved Hide resolved

sand4rt mentioned this pull request Oct 29, 2023

Support for Angular 16 sand4rt/playwright-ct-angular#23

Open

sand4rt force-pushed the hello-angular-ct branch from 720980b to 71599da Compare November 5, 2023 16:22

sand4rt force-pushed the hello-angular-ct branch from 71599da to 8ccb3bb Compare November 5, 2023 20:51

This comment has been minimized.

Sign in to view

mgechev reviewed Nov 17, 2023

View reviewed changes

tests/components/ct-angular/src/assets/logo.svg Outdated Show resolved Hide resolved

sand4rt mentioned this pull request Nov 20, 2023

Support for non standalone angular component sand4rt/playwright-ct-angular#35

Open

yjaaidi mentioned this pull request Nov 21, 2023

feat(ct): generate angular ct project microsoft/create-playwright#106

Open

This was referenced Nov 27, 2023

[Feature] Web Component (Lit) support for test-ct #14241

Open

RFC: Introduce Analog application builder/dev-server analogjs/analog#770

Closed

sand4rt mentioned this pull request Feb 18, 2024

[Bug]: Angular/Web component tests fail with .ts or .js as file extension #29544

Open

yjaaidi mentioned this pull request Feb 23, 2024

Add support for Angular 17 sand4rt/playwright#5

Merged

7 tasks

sand4rt force-pushed the hello-angular-ct branch from 9e88b09 to 31e8817 Compare February 25, 2024 15:51

sand4rt force-pushed the hello-angular-ct branch from 31e8817 to 3226aa5 Compare March 26, 2024 13:45

This comment has been minimized.

Sign in to view

sand4rt mentioned this pull request May 10, 2024

Components are not compiled sand4rt/playwright-ct-angular#52

Closed

dgozman reviewed May 14, 2024

View reviewed changes

chronospatian reviewed May 15, 2024

View reviewed changes

tests/components/ct-angular/playwright.config.mts Show resolved Hide resolved

chronospatian reviewed May 15, 2024

View reviewed changes

tests/components/ct-angular/tests/events.spec.ts Show resolved Hide resolved

tests/components/ct-angular/tests/events.spec.ts Show resolved Hide resolved

tests/components/ct-angular/tests/update.spec.ts Show resolved Hide resolved

fix(ct): angular unused file

a018a27

core: remove duplicate test

666a18d

timdeschryver reviewed May 20, 2024

View reviewed changes

packages/playwright-ct-angular/registerSource.mjs Show resolved Hide resolved

sand4rt mentioned this pull request May 24, 2024

feat(ct): class and object components #30269

Open


		/** @typedef {import('../playwright-ct-core/types/component').ObjectComponent} ObjectComponent */

		import 'zone.js';

		@@ -0,0 +1,45 @@
		# See http://help.github.com/ignore-files/ for more about ignoring files.

feat(ct): angular component testing #27783

Are you sure you want to change the base?

feat(ct): angular component testing #27783

Conversation

sand4rt commented Oct 24, 2023 • edited

TODO

This comment has been minimized.

This comment has been minimized.

pavelfeldman commented Oct 25, 2023

yjaaidi left a comment

Choose a reason for hiding this comment

yjaaidi commented Oct 25, 2023 • edited

sand4rt commented Oct 27, 2023

edbzn left a comment

Choose a reason for hiding this comment

sand4rt commented Nov 5, 2023 • edited

This comment has been minimized.

yjaaidi commented Nov 13, 2023

yjaaidi commented Nov 21, 2023 • edited

yjaaidi commented Feb 15, 2024

flobacher commented Feb 15, 2024

sand4rt commented Feb 22, 2024

yjaaidi commented Feb 23, 2024 • edited

maartentibau commented Feb 27, 2024

zargham-leanix commented Mar 20, 2024

This comment has been minimized.

sand4rt commented May 10, 2024

rainerhahnekamp commented May 11, 2024

sand4rt commented May 11, 2024

rainerhahnekamp commented May 11, 2024

maartentibau commented May 12, 2024

chronospatian commented May 13, 2024 • edited

yjaaidi commented May 13, 2024

yjaaidi commented May 13, 2024

chronospatian commented May 13, 2024 • edited

chronospatian commented May 13, 2024 • edited

sand4rt commented May 13, 2024

chronospatian commented May 13, 2024

yjaaidi commented May 13, 2024

chronospatian commented May 13, 2024

chronospatian commented May 14, 2024 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

chronospatian commented May 15, 2024 • edited

chronospatian May 15, 2024 • edited

Choose a reason for hiding this comment

chronospatian left a comment

Choose a reason for hiding this comment

chronospatian commented May 15, 2024

github-actions bot commented May 15, 2024

Test results for "tests 1"

github-actions bot commented May 16, 2024

Test results for "tests 1"

chronospatian commented May 24, 2024

sand4rt commented Oct 24, 2023 •

edited

yjaaidi commented Oct 25, 2023 •

edited

sand4rt commented Nov 5, 2023 •

edited

yjaaidi commented Nov 21, 2023 •

edited

yjaaidi commented Feb 23, 2024 •

edited

chronospatian commented May 13, 2024 •

edited

chronospatian commented May 13, 2024 •

edited

chronospatian commented May 13, 2024 •

edited

chronospatian commented May 14, 2024 •

edited

chronospatian commented May 15, 2024 •

edited

chronospatian May 15, 2024 •

edited