-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Path.toBeASymbolicLink #765
Comments
I vote to name the function |
Good with me, I was considering it as well (already did it for the infix API) |
I'll work on this |
@fimbulwint note that I have updated the description. Have fun implementing and let us know in case you need help |
@robstoll Thanks! |
@robstoll I'm ready to create a PR, but I don't have permissions to push/create the tracking branch |
@fimbulwint you should fork this repository, push the branch to your fork, and then open a Pull Request from your fork. See also Creating a Pull Request from a Fork. |
@jGleitz thank you, done that now |
add convenience shortcut for `Path.toBeASymbolicLink` feature
Platform (all, jvm, js): all
Extension (none, kotlin 1.3): none
Code related feature
Following the things you need to do:
logic
toBeASymbolicLink
(see isRegularFile as a guideline)api-fluent
toBeASymbolicLink
(see isRegularFile as a guideline)@since 0.16.0
(adapt to current milestone) to KDOCapi-infix
toBe
which expect a new pseudo-keywordaSymbolicLink
(see toBe(aRegularFile)` as a guideline)@since 0.16.0
(adapt to current milestone) to KDOCtoBe aSymbolicLink
to PathExpectationsSpec in specs-common adopt the spec in api-fluentYour first contribution?
I'll work on this
if you would like to take this issue over.This way we get the chance to revise the description in case things have changed in the meantime, we might give you additional hints and we can assign the task to you, so that others do not start as well.
(Invite yourself in case you do not have an account yet).
The text was updated successfully, but these errors were encountered: