Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Test] Symfony framework dagger module#59240

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
dragoonis wants to merge4 commits intosymfony:7.4
base:7.4
Choose a base branch
Loading
fromdragoonis:7.3

Conversation

dragoonis
Copy link

…ions

QA
Branch?7.3 for features / 5.4, 6.4, 7.1, and 7.2 for bug fixes
Bug fix?no
New feature?yes
Deprecations?no
Issuesnone
LicenseMIT

As per strategic calls with@nicolas-grekas and@welcoMattic and others..

I am creating the official Dagger module for the Symfony project .. here is there initial POC.

Let's work together to ensure all flags to the respective libraries are being preserved.

there may be some different flags for local running versus inside github runners, perhaps? let's explore together 🚀

chapterjason, kaznovac, mykiwi, qdequippe, and codedmonkey reacted with eyes emoji
@dragoonisdragoonis changed the title[Test] Symfony framework dagger module - adding static analysis funct…[Test] Symfony framework dagger moduleDec 18, 2024
#[DaggerFunction]
#[Doc('Run phpstan across the entire symfony codebase')]
// dagger call phpstan --source=.
public function phpstan(Directory $source): Container
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not add a default to the right directory ?

Copy link
Author

@dragoonisdragoonisDec 21, 2024
edited
Loading

Choose a reason for hiding this comment

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

@Neirda24 it's yin/yang .. do we really wanna phpstan the entire codebase? or just make it configurable to the caller

the best practise (Dagger best practises) isn't to hard code anything in the code, and instead just change the CLI arguments for different paths .. and that's why I've done it like this, to follow convention

let's discuss this on our next call, after I've got integration tests working..

@@ -0,0 +1,18 @@
{
"name": "symfony",
"engineVersion": "v0.15.1",
Copy link
Contributor

Choose a reason for hiding this comment

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

what would be the process to keep this up to date ? A bot opening a PR automatically or only if its fails then we need to upgrade.

Copy link
Author

Choose a reason for hiding this comment

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

@Neirda24 hey! we will manually bump this every time we want to, or need to. Since I'm from Dagger, then I'll know exactly what important stuff is being released and if it's worth the upgrade or not

mykiwi added a commit to SymfonyCon/2024-talks that referenced this pull requestDec 24, 2024
@symfonysymfony deleted a comment fromcarsonbotJan 7, 2025
@symfonysymfony deleted a comment fromcarsonbotJan 7, 2025
@fabpotfabpot modified the milestones:7.3,7.4May 26, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@Neirda24Neirda24Neirda24 left review comments

Assignees
No one assigned
Projects
None yet
Milestone
7.4
Development

Successfully merging this pull request may close these issues.

4 participants
@dragoonis@Neirda24@fabpot@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp