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

rename: list_recent_scans --> listruns #224

Closed
prjemian opened this issue Aug 15, 2019 · 3 comments · Fixed by #229
Closed

rename: list_recent_scans --> listruns #224

prjemian opened this issue Aug 15, 2019 · 3 comments · Fixed by #229
Assignees
Milestone

Comments

@prjemian
Copy link
Contributor

shorter, easier to explain

Is scanlist a better choice?

@prjemian prjemian added this to the 1.1.12 milestone Aug 15, 2019
@prjemian prjemian self-assigned this Aug 15, 2019
@prjemian
Copy link
Contributor Author

alias the old name, but report as deprecated

@prjemian prjemian changed the title rename: list_recent_scans --> catalog rename: list_recent_scans --> scanlist Aug 15, 2019
@prjemian
Copy link
Contributor Author

Use scanlist since catalog may be associated with plan_catalog (an early application)

@prjemian prjemian changed the title rename: list_recent_scans --> scanlist rename: list_recent_scans --> listruns Aug 15, 2019
@prjemian
Copy link
Contributor Author

Keep list first and focus on the bluesky term run: listruns

prjemian added a commit that referenced this issue Aug 15, 2019
prjemian added a commit that referenced this issue Aug 15, 2019
prjemian added a commit that referenced this issue Aug 15, 2019
prjemian added a commit that referenced this issue Aug 15, 2019
prjemian added a commit that referenced this issue Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant