Skip to content
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

Prefer snapshot to resolver, while maintaining them as synoynms #6466

Closed
8 of 11 tasks
mpilgrem opened this issue Jan 31, 2024 · 0 comments
Closed
8 of 11 tasks

Prefer snapshot to resolver, while maintaining them as synoynms #6466

mpilgrem opened this issue Jan 31, 2024 · 0 comments
Assignees

Comments

@mpilgrem
Copy link
Member

mpilgrem commented Jan 31, 2024

Building on #4256:

Capable of being included in Stack 2.15.1, because they do not interfere with users' current practices:

  • Introduce --snapshot as a synonym for --resolver
  • Introduce config set snapshot command, corresponding to config set resolver
  • Prefer the snapshot: key to resolver: in Stack's online examples and in-app messages
  • Prefer --snapshot to --resolver in Stack's online examples and in-app messages
  • Put 'snapshot' ahead of 'resolver' in Stack's online documentation where synonyms introduced
  • Refer to 'snapshot' or 'snapshot resolver' in in-app messages where 'resolver' is currently used.
  • Use snapshot: in Stack's tests
  • Use snapshot: in Stack's own project-level configuration files

Better delayed to post-Stack 2.15.1 and its adoption by GitHub-hosted runners

  • Prefer snapshot: to resolver: in stack init
  • Update the instance ToJSON Project to use snapshot: for the resolver field
  • Possibly, rename the resolver field of the Package type snapshot
@mpilgrem mpilgrem self-assigned this Jan 31, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 1, 2024
mpilgrem added a commit that referenced this issue Feb 2, 2024
mpilgrem added a commit that referenced this issue Feb 2, 2024
mpilgrem added a commit that referenced this issue Feb 2, 2024
mpilgrem added a commit that referenced this issue Feb 2, 2024
mpilgrem added a commit that referenced this issue Feb 15, 2024
mpilgrem added a commit that referenced this issue Feb 15, 2024
mpilgrem added a commit that referenced this issue Feb 15, 2024
mpilgrem added a commit that referenced this issue Feb 15, 2024
Re #6466 stack init prefers snapshot to resolver
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant