Sitelet https://github.com/DragonBox/uplift/pull/60
Skip to content

Menu Items: Make installation from menu clearer - #60

Merged
niezbop merged 2 commits into
DragonBox:masterfrom
niezbop:menu/install_items
Apr 30, 2018
Merged

niezbop merged 2 commits into
DragonBox:masterfrom
niezbop:menu/install_items

Conversation

@niezbop

@niezbop niezbop commented Apr 25, 2018 •

Copy link
Copy Markdown
Member

A lot of feedback tend to show that there was a confusion regarding what was doing what between "Debug/Install from lockfile" and "Install Dependencies". This moves the lockfile installation out of the debug section as it is not a debug-only feature and is used quite frequently.
Moreover, this clarifies the messages to better explain the difference between the installation methods.

A lot of feedback tend to show that there was a confusion regarding what
was doing what between "Debug/Install from lockfile" and "Install
Dependencies". This moves the lockfile installation out of the debug
section as it is not a debug-only feature and is used quite frequently.
Moreover, this clarifies the messages to better explain the difference
between the installation methods.
@niezbop
niezbop requested a review from lacostej April 25, 2018 14:24
@lacostej

Copy link
Copy Markdown
Member

By moving it first aren't we modifying the default user behavior?

See also

image

for reference

@lacostej lacostej left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

see question above

@niezbop

niezbop commented Apr 30, 2018 •

Copy link
Copy Markdown
Member Author

We are not really modifying the default user behaviour actually, at least not the way it is currently in use right now. "Install Dependencies" tries to update all dependencies, regardless of the fact that they were changed in the Upfile or not. Therefore, the comparison with the Bundler is short lived, as we do not have the conservative update type behaviour. The behaviour promoted by "Install Dependencies" is the "bundle update" which is not what we want. Currently we should fix the dependency solving mechanism before anything to be able to put forward the correct behaviours, but this require a bit of time to implement it.

Edit: We are not really modifying the default user behaviour because most people do not use "Install Dependencies", as it has side effects that they do not want, and resort to "Install from Lockfile" + update window. Therefore, we make it more straight forward and easier to understand.

}

[MenuItem("Tools/Uplift/Install Dependencies", false, 2)]
[MenuItem("Tools/Uplift/Install and upgrade dependencies", false, 3)]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Update dependencies


[MenuItem("Tools/Uplift/Install Dependencies", false, 2)]
[MenuItem("Tools/Uplift/Install and upgrade dependencies", false, 3)]
private static void InstallDependencies()

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

rename method?

}


[MenuItem("Tools/Uplift/Install exact dependencies", false, 2)]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What happens if no lock file?

@niezbop niezbop Apr 30, 2018 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It throws!

else if(strategy == InstallStrategy.ONLY_LOCKFILE)
{
  if(!present)
    throw new ApplicationException("Uplift cannot install dependencies in strategy ONLY_LOCKFILE if there is no lockfile");

  targets = LoadLockfile().installableDependencies;
}

@niezbop
niezbop merged commit 5c9b6a2 into DragonBox:master Apr 30, 2018
@niezbop
niezbop deleted the menu/install_items branch April 30, 2018 11:01
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.

2 participants