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

Add Fake.Rsync #1987

Merged
merged 4 commits into from
Jul 21, 2018
Merged

Add Fake.Rsync #1987

merged 4 commits into from
Jul 21, 2018

Conversation

MangelMaxime
Copy link
Contributor

@MangelMaxime MangelMaxime commented Jun 8, 2018

I started adding Fake.Rsync module.

I am creating this PR to check if this is building and if I didn't forget to do something. Taking too much time on my machine. :)

@MangelMaxime
Copy link
Contributor Author

MangelMaxime commented Jun 8, 2018

@matthid
Do I need to create an empty version of AssemblyInfo.fs ?

Error:

fatal: Unable to mark file src/app/Fake.Rsync/AssemblyInfo.fs
�=Finished (Failed) 'SetAssemblyInfo' in 00:00:01.4031626

@matthid
Copy link
Member

matthid commented Jun 9, 2018

Yes or copy one from another project. Not exactly sure why. I guess we first try to ignore changes with git and then create the file afterwards. I guess we need to re-order that or do it twice (and check if the file exists first)

@matthid
Copy link
Member

matthid commented Jun 13, 2018

ping :)

@MangelMaxime
Copy link
Contributor Author

Sorry i am at NDC Oslo.

I will try to do it tomorrow.

@matthid
Copy link
Member

matthid commented Jun 13, 2018

@MangelMaxime Don't worry and no need to be sorry. Have fun! :)

@MangelMaxime
Copy link
Contributor Author

@matthid Ok the CI is green now :)

Copy link
Member

@matthid matthid left a comment

Choose a reason for hiding this comment

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

Some minor nits left

///
/// ## Sample
///
/// let result =
Copy link
Member

Choose a reason for hiding this comment

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

I believe it needs to be indented further in order to be formatted as code in the docs.

static member WithDestination dest options =
{ options with Destination = dest }

let rec actionToString =
Copy link
Member

Choose a reason for hiding this comment

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

could be private/internal?

Trace.traceError msg
results.Add (ConsoleMessage.CreateError msg)

let messageF msg =
Copy link
Member

Choose a reason for hiding this comment

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

I always thought we have a helper collecting the messages for you already. But I guess you wanted to have "live"-output?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes ,I think having them live make more sense. And also, I believe I did that to get the right output color too.

@MangelMaxime
Copy link
Contributor Author

I completely forgot about this PR, I update it on Monday

@MangelMaxime
Copy link
Contributor Author

@matthid I took your comments in account.

For the > synthax, this is the only way I found to have a nice display.

@matthid matthid changed the base branch from master to release/next July 21, 2018 16:28
@matthid
Copy link
Member

matthid commented Jul 21, 2018

Yes I might take a look at the docs on staging, lets see...

@matthid matthid merged commit 16e48d6 into fsprojects:release/next Jul 21, 2018
@matthid
Copy link
Member

matthid commented Jul 21, 2018

Thanks for this new feature :)

@MangelMaxime
Copy link
Contributor Author

For the need of ‘> this is probably due to a bug in Ionide display.

I am working on fixing it. When released I will take a look back to this module documentation.

Releasing in current stage still make sense 😊

@matthid
Copy link
Member

matthid commented Jul 22, 2018

Ugs no idea how I missed it, but there are seem to be some problems with this:

  • It is missing from the API-Docs completely https://staging.fake.build/apidocs/v5/index.html
  • It is missing in the menu:
    image
  • It should be in the Fake.Tools (ie Fake.Tools.Rsync) namespace instead of Fake,Rsync (IIRC the first problem is a direct consequence of this because of globbing)

@matthid
Copy link
Member

matthid commented Jul 22, 2018

You can take a look at https://staging.fake.build

@MangelMaxime
Copy link
Contributor Author

Is it because the namespace is: namespace Fake.Rsync compared to module Fake.Tools.Git ?

@matthid
Copy link
Member

matthid commented Jul 22, 2018

No I think it is because:

  • I think the API reference is generated via globbing over Fake.Tools.* and Fake.Core.* (and some others). But we have to take a look to be sure.
  • The menu is actually created by hand in help/templates/template.csproj and I would have added it myself, but I couldn't add the entry because I couldn't find the API reference to link to ;)

@matthid matthid mentioned this pull request Jul 22, 2018
@matthid
Copy link
Member

matthid commented Jul 29, 2018

Any chance you can take a look? Otherwise I might revert this for the next release until we are ready :)
(Or maybe I'm just fixing the outstanding things myself we will see how fast I can fix the other things - just wanted to be transparent beforehand).

@MangelMaxime
Copy link
Contributor Author

I was thinking you were looking into it :)

Also, I have no idea how the docs site of FAKE works. If you don't take a look I will try to a look at it tomorrow or after tomorrow

matthid added a commit that referenced this pull request Jul 29, 2018
@matthid
Copy link
Member

matthid commented Jul 29, 2018

Nevermind, it looks like it was easy enough :). My analysis was incorrect - probably all that was missing was adding it to the Fake.sln solution...

@MangelMaxime
Copy link
Contributor Author

Ah yes, correct I don't use the *.sln file in general so I forgot to add it :)

Thanks you for taking a look at it. I would have search for a long time :)

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