Implement component-level access control mechanism #61
Conversation
StevenJiang1110
force-pushed
the
components
branch
2 times, most recently
from
cc4c8b5
to
b98df13
Compare
| analysis/target | ||
| analysis/Cargo.lock | ||
| tests/*/Cargo.lock | ||
| tests/*/target |
There was a problem hiding this comment.
Cargo.lock files under tests are ignored, but they are still added for version control. Is this a mistake?
There was a problem hiding this comment.
Since in this case, each library under tests is an independent crate, they will generate an Cargo.lock when execute cargo component check on it. But such files can be removed at last step of test instead of added to .gitignore. I removed these lines from .gitignore.
| @@ -0,0 +1,246 @@ | |||
| //! This implementation is from rust clippy | |||
There was a problem hiding this comment.
Add the license of rust clippy as the file header. Remember to add Ant Group as the latest copyright holder.
| @@ -0,0 +1,129 @@ | |||
| //! This implementation is from rust clippy | |||
There was a problem hiding this comment.
Add the license of rust clippy as the file header. Remember to add Ant Group as the latest copyright holder.
README.md
Outdated
| @@ -55,6 +55,15 @@ all developmennt tools are installed. | |||
| make setup | |||
| ``` | |||
|
|
|||
| Then, install some standalone tools. | |||
There was a problem hiding this comment.
Then, install some standalone tools (e.g., `cargo-component-check`) under the project directory.
StevenJiang1110
force-pushed
the
components
branch
from
b98df13
to
f6f87ec
Compare
tatetian
changed the title
No description provided.