Skip to content

[DX] Command to list all available recipes #562

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

Closed
wants to merge 0 commits into from

Conversation

maxhelias
Copy link
Contributor

@maxhelias maxhelias commented Sep 18, 2019

First step of #518, the command symfony:recipes:show and alias symfony:recipes

Result :
Capture d’écran 2019-09-18 à 15 46 09

I need feedback on the disposition and maybe i can add the version of the recipe installed like

  • doctrine/annontations 1.0

Tell me what you think :)

Note: the last section is currently commented out, and will be added later

@maxhelias maxhelias force-pushed the feature/recipe-list branch 2 times, most recently from 032d7d6 to 5ed8416 Compare September 19, 2019 15:29
@maxhelias maxhelias force-pushed the feature/recipe-list branch from 5ed8416 to f26a79a Compare October 10, 2019 08:17
@maxhelias maxhelias requested a review from weaverryan October 10, 2019 08:20
@maxhelias
Copy link
Contributor Author

friendly ping @weaverryan 😄

//$write[] = '';
//$write[] = '<fg=blue>Run</>:';
//$write[] = ' * composer symfony:recipes vendor/package to see details about a recipe.';
//$write[] = ' * composer symfony:recipes:update vendor/package to update that recipe.';
Copy link
Member

Choose a reason for hiding this comment

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

I think to make this new command "complete", we would need to at least be able to show 2 commands down here:

A) A command to "update" a single recipe - so symfony:recipe:update - item (3) from #518
B) A command to "install" missing recipes - so symfony:recipe:install - item (2) from #518

The symfony:recipes vendor/package or whatever we call it - item (4) from #518 would be super nice to have, as would symfony:recipes:blame - but those could come later.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

  • I started the symfony:recipes vendor/package in this command. I will update this PR when it's ready
  • The symfony:recipes:install is ready here : Rename SyncRecipes on InstallRecipes #565
  • For the symfony:recipes:update, it would be better to have some feedback on the Rename SyncRecipes on InstallRecipes #565 before I start it
  • And for the symfony:recipes:blame, it will be a lot more complicated and I agree to do it later

@maxhelias maxhelias force-pushed the feature/recipe-list branch from f26a79a to 96a33d4 Compare November 7, 2019 12:48
@maxhelias
Copy link
Contributor Author

maxhelias commented Nov 13, 2019

I updated the PR, there is now the possibility to inspect only one recipe
Here is an overview, make suggestions for the final rendering 😉

Capture d’écran 2019-11-13 à 15 30 37

@maxhelias maxhelias force-pushed the feature/recipe-list branch 2 times, most recently from bfc6676 to a8d5c94 Compare December 9, 2019 22:48
fabpot added a commit that referenced this pull request Dec 11, 2019
This PR was merged into the 1.5-dev branch.

Discussion
----------

Allowing specific recipes to be "re-installed"

Hi!

Very simple: you can now re-install/update just one (or specific) recipes:

```
composer symfony:sync-recipes symfony/console --force
```

That's very helpful, as there are a few specific recipes (this is one of them) that really *do* need to be "updated", at the very least, when upgrading to Symfony 5 (as some important files have evolved over time).

This relates to #575 (will help with upgrading), #518 and should go along with the PRs #562 and #565

Thanks!

Commits
-------

a9dad87 Allowing specific recipes to be "re-installed"
@maxhelias maxhelias force-pushed the feature/recipe-list branch 2 times, most recently from 739326e to decdf61 Compare December 12, 2019 13:57
Copy link
Member

@weaverryan weaverryan left a comment

Choose a reason for hiding this comment

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

nit picks :)

Copy link
Member

@weaverryan weaverryan left a comment

Choose a reason for hiding this comment

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

This is ready - dependent on #565 (just because this command references the new/renamed recipes:installcommand).

@nicolas-grekas
Copy link
Member

Can you please rebase the PR?
Maybe also update the screenshots to help next reviewers?

@maxhelias
Copy link
Contributor Author

Here is the result :

Capture d’écran 2019-12-13 à 17 08 36

Capture d’écran 2019-12-13 à 17 09 25

@nicolas-grekas
Copy link
Member

Thank you @maxhelias.

nicolas-grekas added a commit that referenced this pull request Dec 13, 2019
This PR was squashed before being merged into the 1.5-dev branch.

Discussion
----------

[DX] Command to list all available recipes

First step of #518, the command `symfony:recipes:show` and alias `symfony:recipes`

Result :
<img width="701" alt="Capture d’écran 2019-09-18 à 15 46 09" src="https://user-images.githubusercontent.com/12966574/70814407-b4f8eb00-1dcb-11ea-9118-454d444cd22d.png">

I need feedback on the disposition and maybe i can add the version of the recipe installed like
 - doctrine/annontations 1.0

Tell me what you think :)

Note: the last section is currently commented out, and will be added later

Commits
-------

f73fba0 [DX] Command to list all available recipes
@nicolas-grekas
Copy link
Member

(dunno what happened to the attached patch but the commit is in:
77a0cc9)

nicolas-grekas added a commit that referenced this pull request Dec 13, 2019
… (weaverryan)

This PR was squashed before being merged into the 1.5-dev branch.

Discussion
----------

Adding the current recipe URL to recipes <recipe> output

Hi!

This replaces #585 and builds off of #562.

Basically, I *thought* that it would be nearly impossible to get the *exact* git sha for when a recipe is installed. But with a few API calls to GitHub, it's quite possible :). This gives us the ability to (at least) give the URL to the *exact* state of the recipe when it was installed in their app. This can help them determine what's changed and if they need to update.

Giving them a "diff" URL would be even more awesome - but as the directory often changes - I don't believe there is any URL we can give to visually compare across directories. Output:

<img width="1278" alt="Screen Shot 2019-12-12 at 12 06 54 PM" src="https://user-images.githubusercontent.com/121003/70733308-13dd3800-1cd8-11ea-85c8-61c3283dc1b4.png">

The "installed recipe" is the line that this enables. The "new commits" line (unfortunately) can only be shown when the version/directory of the recipe hasn't changed. There's just not good way (that I can think of) to show a decent history if they are upgrading from (for example) `symfony/framework/bundle/3.3` to `symfony/framework-bundle/4.2`.

Cheers!

Commits
-------

a761365 Adding the current recipe URL to recipes <recipe> output
@maxhelias maxhelias deleted the feature/recipe-list branch August 21, 2020 12:08
tgalopin pushed a commit to tgalopin/flex that referenced this pull request Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants