Skierkowski Grzegorz

So your solution is conceptually the same as mine. Repeating permission checking on each resolver doesn't sound good for me, that's why I mentioned GraphQLite solution. > Defining authorization logic...

Inside standard middleware I have no direct access to `$root, $args, $context, $resolveInfo` variables, but middleware specifically for GraphQL would do the job.

This is a main part: ```php // Discussion.php /** * @ORM\ManyToMany(targetEntity="Tag", inversedBy="discussions") * @ORM\JoinTable(name="tags_discussions") */ public Collection $tags; /** * @GraphQL\Field(name="tags", listOf=Tag::class) * @GraphQL\Args( * { * @GraphQL\Field(name="first", type="Int", nullable=true),...

There are colorful labels rendered near the test title in the HTML report right now, so I believe the tags from the title could be automatically removed. The same could...

I consider it a good stuff. There could be an additional parameter in the config, similar to `forbidOnly` to handle this.

This method is not designed to modify the test title. Could you provide more context about your use case? If you want to add the tag to all of the...

Does this solution satisfy you? ```js const customTest = function(title, callback) { return test(`${title} @tag`, callback) } customTest.fixme = function(title, callback) { return test.fixme(`${title} @tag`, callback) } // etc. ```

```js import { test } from '@playwright/test' const customTest = function(title, callback) { return test(`${title} @tag`, callback) } customTest('title', async ({ page }) => { await page.goto('https://playwright.dev') }) ``` ```...

@dgozman It sounds reasonable enough to me. Also, I can confirm that handling it manually works without any issues.

Did you already add `userName` fixture (value, not only the type)? Did you try to start your tests anyway?