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

Shards subcommands #28

Merged
merged 8 commits into from Mar 31, 2016

Conversation

Projects
None yet
2 participants
@White-Oak
Contributor

White-Oak commented Mar 24, 2016

Implemented add <name> and remove <name>.

Currently, they add and remove 'features' from Cargo.toml of a project.

No tests, cause not sure how to test this. Maybe try to build a project?

This is an implementation of CLI task in Shards RFC.

@ebkalderon

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Mar 24, 2016

Member

@White-Oak Hmm, it is too early to properly test this feature since we don't have a concrete implementation of the engine modules concept. Nor do we have any Cargo features in the engine to actually try, and we don't have a spec for zipped modules.

Member

ebkalderon commented Mar 24, 2016

@White-Oak Hmm, it is too early to properly test this feature since we don't have a concrete implementation of the engine modules concept. Nor do we have any Cargo features in the engine to actually try, and we don't have a spec for zipped modules.

@White-Oak

This comment has been minimized.

Show comment
Hide comment
@White-Oak

White-Oak Mar 24, 2016

Contributor

@ebkalderon It's a part one of "modules/shards" project, featuring "features".

Contributor

White-Oak commented Mar 24, 2016

@ebkalderon It's a part one of "modules/shards" project, featuring "features".

@ebkalderon

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Mar 24, 2016

Member

@White-Oak We should probably make an RFC for this, given the discussion we were all having on the general room. Implementing this properly might be an involved process.

Member

ebkalderon commented Mar 24, 2016

@White-Oak We should probably make an RFC for this, given the discussion we were all having on the general room. Implementing this properly might be an involved process.

@White-Oak

This comment has been minimized.

Show comment
Hide comment
@White-Oak

White-Oak Mar 24, 2016

Contributor

@ebkalderon Certainly. But this is "the part one" as I mentioned erlier, so apart from naming it and naming commands it wouldn't have much alternatives (:

Contributor

White-Oak commented Mar 24, 2016

@ebkalderon Certainly. But this is "the part one" as I mentioned erlier, so apart from naming it and naming commands it wouldn't have much alternatives (:

@White-Oak White-Oak referenced this pull request in amethyst/amethyst Mar 25, 2016

Closed

RFC: Extensions system "Shards" #34

1 of 7 tasks complete

@White-Oak White-Oak changed the title from Module subcommand to Shards subcommands Mar 25, 2016

@White-Oak

This comment has been minimized.

Show comment
Hide comment
@White-Oak

White-Oak Mar 25, 2016

Contributor

@ebkalderon if we agreed on CLI task in RFC for shards, this is ready to be merged.

Contributor

White-Oak commented Mar 25, 2016

@ebkalderon if we agreed on CLI task in RFC for shards, this is ready to be merged.

@ebkalderon

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Mar 29, 2016

Member

@White-Oak It looks like there are some conflicts with this pull request? Could you please resolve them? I think this is ready to be merged. We can keep discussing specifics on the shards RFC (amethyst/amethyst#34) and iterate on this as needed.

Member

ebkalderon commented Mar 29, 2016

@White-Oak It looks like there are some conflicts with this pull request? Could you please resolve them? I think this is ready to be merged. We can keep discussing specifics on the shards RFC (amethyst/amethyst#34) and iterate on this as needed.

@White-Oak

This comment has been minimized.

Show comment
Hide comment
@White-Oak

White-Oak Mar 29, 2016

Contributor

@ebkalderon sure! I'll do it asap

Contributor

White-Oak commented Mar 29, 2016

@ebkalderon sure! I'll do it asap

@White-Oak

This comment has been minimized.

Show comment
Hide comment
@White-Oak

White-Oak Mar 29, 2016

Contributor

@ebkalderon Renamed modules to shards and used amethyst add <name> as a syntax.

Contributor

White-Oak commented Mar 29, 2016

@ebkalderon Renamed modules to shards and used amethyst add <name> as a syntax.

@ebkalderon

This comment has been minimized.

Show comment
Hide comment
@ebkalderon

ebkalderon Mar 31, 2016

Member

Sorry for the delayed response. I think this pull request is essentially done, despite our inability to effectively test it. I'll merge this now!

Member

ebkalderon commented Mar 31, 2016

Sorry for the delayed response. I think this pull request is essentially done, despite our inability to effectively test it. I'll merge this now!

@ebkalderon ebkalderon merged commit 33ceccb into amethyst:master Mar 31, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

@ebkalderon ebkalderon referenced this pull request Apr 2, 2016

Closed

Refactor internal subcommand API for build tool #33

0 of 6 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment