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 maintenance struct key from value to status #996

Merged
merged 1 commit into from
Aug 22, 2017
Merged

Rename maintenance struct key from value to status #996

merged 1 commit into from
Aug 22, 2017

Conversation

vignesh-sankaran
Copy link
Contributor

Feel status is a better name for the Maintenance struct key than value. I also renamed the MaintenanceValue enum to MaintenanceStatus.

@carols10cents
Copy link
Member

Fine with me!

bors: r+

bors-voyager bot added a commit that referenced this pull request Aug 22, 2017
996: Rename maintenance struct key from value to status r=carols10cents

Feel status is a better name for the `Maintenance` struct key than value. I also renamed the `MaintenanceValue` enum to `MaintenanceStatus`.
@bors-voyager
Copy link
Contributor

bors-voyager bot commented Aug 22, 2017

Build succeeded

@bors-voyager bors-voyager bot merged commit 3ba2b8f into rust-lang:master Aug 22, 2017
@vignesh-sankaran vignesh-sankaran deleted the rename-maintenance-key branch August 22, 2017 12:17
bors-voyager bot added a commit that referenced this pull request Aug 30, 2017
952: Maintenence badge front end r=carols10cents

Start front end work for #704 by creating a maintenance badge component. I'm not quite sure what the alias() function does in ember.js, think it takes out the attributes from the badges for a crate?

I'm going to work on all the frontend changes here, since the tests failed when I attempted to add the fixture without the badge component.

NOTE: If #996 is approved, I'll have to change this PR to work with it.
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