{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":693366890,"defaultBranch":"master","name":"pytest-mypy-plugins","ownerLogin":"Delgan","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2023-09-18T22:23:05.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/4193924?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1699131188.0","currentOid":""},"activityList":{"items":[{"before":"e7b7a9dab3559f02406401e105312c295e32ada4","after":"0f10c945e0353bba1984d9e1c6c8743ea0c3ca88","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-05T21:54:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"3ec229740b7516c751820df6cc6a3e4c5f5549d2","after":"e7b7a9dab3559f02406401e105312c295e32ada4","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-05T21:48:06.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"050fb9bc64c98de5456986dcc8714fd3536fb661","after":"3ec229740b7516c751820df6cc6a3e4c5f5549d2","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-05T21:44:26.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"ea61ad5d30bd68aed9a256d0aaa64247de56e564","after":"050fb9bc64c98de5456986dcc8714fd3536fb661","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-04T22:21:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"27437f0eb2e710823966d4d450dd680556587bed","after":"ea61ad5d30bd68aed9a256d0aaa64247de56e564","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-04T22:17:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"1e23359a31f7e874440ecce9bfe25e0784c46eef","after":"27437f0eb2e710823966d4d450dd680556587bed","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-04T21:47:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"e908b631f345b785908b57b79b1cc15adfc8bccb","after":"1e23359a31f7e874440ecce9bfe25e0784c46eef","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-04T21:44:34.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":null,"after":"e908b631f345b785908b57b79b1cc15adfc8bccb","ref":"refs/heads/GH-133-add-plugin-config","pushedAt":"2023-11-04T20:53:08.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Add Mypy configuration through root \"pyproject.toml\" file\n\nIt is not uncommon to require a Mypy configuration that differs from the project's main\nconfiguration and is specific to tests, such as enabling the 'force_uppercase_builtins'\noption. Currently, the argument '--mypy-pyproject-toml-file' can be used via the command\nline, but this approach has two drawbacks:\n\n- It requires an additional file in the codebase, whereas it is more pleasant to\n group all configurations in the root 'pyproject.toml' file.\n- It confines the invocation of 'pytest' to a fixed location, as the path is resolved\n relative to the current working directory. However, there are situations where it is\n useful to call 'pytest' from a different directory.\n\nThe solution implemented here allows for configuring the Mypy parameters used by\n'pytest-mypy-plugins' directly within the project's 'pyproject.toml' file, addressing\nboth of the aforementioned points.","shortMessageHtmlLink":"Add Mypy configuration through root \"pyproject.toml\" file"}},{"before":"b499462f1a80e7d8ac9d513a24fde5c642a92f26","after":"c80f1eba295c04616c2974eb545934fededaec3c","ref":"refs/heads/master","pushedAt":"2023-11-04T20:52:39.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Fix \"FileNotFoundError\" due to \"schema.json\" not installed (#132)","shortMessageHtmlLink":"Fix \"FileNotFoundError\" due to \"schema.json\" not installed (typeddjan…"}},{"before":"c956df2a6905b2c81cd2dfe82d5b3c0f1aaa010d","after":null,"ref":"refs/heads/patch-2","pushedAt":"2023-09-20T18:43:20.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"}},{"before":"0e7104e4da7e6d9bf0449541962f3cd67c337895","after":"c956df2a6905b2c81cd2dfe82d5b3c0f1aaa010d","ref":"refs/heads/patch-2","pushedAt":"2023-09-20T18:20:34.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Fix \"FileNotFoundError\" due to \"schema.json\" not installed","shortMessageHtmlLink":"Fix \"FileNotFoundError\" due to \"schema.json\" not installed"}},{"before":"b499462f1a80e7d8ac9d513a24fde5c642a92f26","after":"d6a40c25930144c6a4a22ebdb0829bda10fb0e09","ref":"refs/heads/patch-1","pushedAt":"2023-09-18T22:34:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"Delgan","name":null,"path":"/Delgan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/4193924?s=80&v=4"},"commit":{"message":"Ease testing of local stubs by extending \"MYPYPATH\"","shortMessageHtmlLink":"Ease testing of local stubs by extending \"MYPYPATH\""}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADp-b2rAA","startCursor":null,"endCursor":null}},"title":"Activity · Delgan/pytest-mypy-plugins"}