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

two-bucket: Apply new "input" policy #1084

Merged
merged 1 commit into from
Jan 11, 2018

Conversation

ErikSchierboom
Copy link
Member

See #996

Copy link
Member

@rpottsoh rpottsoh left a comment

Choose a reason for hiding this comment

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

lowerCamelCase needs to be applied to this at some point per #987.

@ErikSchierboom
Copy link
Member Author

@rpottsoh WelI spotted. I would prefer to do that in a separate PR.

@ErikSchierboom ErikSchierboom merged commit 15396af into exercism:master Jan 11, 2018
@ErikSchierboom ErikSchierboom deleted the two-bucket-input branch January 11, 2018 08:15
petertseng added a commit to exercism/rust that referenced this pull request Nov 20, 2018
)

Note that two-bucket was added to the Rust track at
#375
At the time it declared 1.0.0 compliance, but was actually compliant
with 1.2.0 already!

Further updates to 1.3.0 and 1.4.0 require no action on the Rust track's
part.

1.0.1: Fix exercise name
exercism/problem-specifications#715

Unversioned(!): Change descriptions
exercism/problem-specifications#716
(Our descriptions are no better or worse, so might as well keep them)

1.1.0: Add cases where goal equals one bucket's capacity
exercism/problem-specifications#763
Rust already had these cases, so just update the descriptions

1.2.0: Fix a test case added in 1.1.0
exercism/problem-specifications#911
exercism/problem-specifications#941
Rust already had the correct values, so no action.

1.3.0: move inputs to `input` object
exercism/problem-specifications#1084

1.4.0: rename JSON keys to camelCase
exercism/problem-specifications#1136
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