## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
Thijs Brobbel
@tiesmaster
Hi all, for PR #595 (and issue #593), I'm trying to get the build to work locally, though, when I run build.cmd, I get the following error:
  MSBuild auto-detection: using msbuild version '14.0' from 'C:\Program Files (x86)\MSBuild\14.0\bin'.
Error reading 'C:\src\references\oss\Humanizer\src\Humanizer.Tests.DotNet\project.json' at line 24 column 23 : TODO: unknown keyword platform
TODO: unknown keyword platform
C:\src\references\oss\Humanizer\build.proj(53,5): error MSB3073: The command ""C:\src\references\oss\Humanizer\tools\NuGet\NuGet.exe" restore "C:\src\references\oss\Humanizer\src\Humanizer.sln"" exited with code 1.
Any ideas?
Alois
@aloisdg
@tiesmaster For build troubleshooting, the best way to handle it is to summon @onovotny
Thijs Brobbel
@tiesmaster
@onovotny Could you maybe help me sort this out? I cannot get the build to work locally, I'm on Update 3, running nuget 3.4.3.855, and have the .NET Core tools installed. Am I missing something?
Florian Foligowski
@subprime
Hi @all, some´body know how to get humanizr work with asp.net core 1.1 ?
Currently i get the following error: The dependency Humanizer.Core.cs 2.1.0 does not support framework .NETCoreApp,Version=v1.1
Oren Novotny
@onovotny
are you using project.json or xproj or csproj?
if project.json/xproj, you need to use humanizer.xproj as the nuget package
for csproj, the regular ones shoudl work
Magnus Lindhe
@mgnslndh
Hi all! How can I get the localized string for a TimeUnit (without the amount)?
Florian Foligowski
@subprime
@onovotny Thanks for this answer. I found the solution some days later.
meghanabendre
@meghanabendre
Hello! First-time contributor here.. Attempting to build the Solution in VS 2015. I get an error about the .csproj file requiring xmlns attribute in <Project> tag. Do I need to upgrade to VS 2017 or can I work off the master?
harishkpv
@harishkpv
@onovotny How do I build the project in VS2015? I noticed it has been recently upgraded to VS2017. Thanks!
Oren Novotny
@onovotny
you can't, sorry
needs VS 2017 but that's a free upgrade
Jason Watson
@jbw
is there a way to use shorthand units e.g. ms instead of milliseconds?
Jason Watson
@jbw
i've just added them to Vocabularies.Default which works fine for my case
Viktorija
@viktorija
Hi everyone, nice to meet you. Has anyone documented how to build the solution? Because it was a bit of challenge.
Oren Novotny
@onovotny
Hi @viktorija you should be able to open it with VS 2017 Update 2 and build
alternatively, it should be working with the .NET Core CLI tools too, so dotnet restore then dotnet build and dotnet test
Viktorija
@viktorija
Thanks @onovotny, builds OK with VS 2017. Submitted a PR at #645, would anyone have a chance to take a look?
Philipe Pinheiro Atela
@philipeatela
Hello everyone. Is there any documentation to help me build the solution on VS 2017? Bit of a beginner here. I downloaded the repository but i can't seem to build it, I'm getting a ton of errors like "Predefined type System.String is not defined or imported"
Mehdi Khalili
@MehdiK
@philipeatela I just cloned the repo to a fresh copy of Win 10 with VS2017 pro, hit rebuild solution and it built everything!
Sonali Patro
@ilanosortap
how do I build from source using visual studio?
Oren Novotny
@onovotny
VS 2017 15.4 or 15.5 can build it
just open the sln file and build
Sonali Patro
@ilanosortap
i cant find the sln file
Martin Strecker
@MaStr11
Sonali Patro
@ilanosortap
how can I find junior jobs or good first bugs?
Martin Strecker
@MaStr11
Martin Strecker
@MaStr11

@ilanosortap

#524

I would like to work on this issue, though i ll need some help

Thanks for helping out. Can you be more specific? What kind of help do you need?

Sonali Patro
@ilanosortap
what changes do i need to make, and where do i need to make them?
basically i might need you to explain the task in simple terms
thanks for helping :)
Martin Strecker
@MaStr11
From the comment on the issue in fluent assertions here https://github.com/fluentassertions/fluentassertions/issues/352#issuecomment-185450646 it seems there is nothing you can do here without breaking things (changes would not be backward compatibility so people upgrading to a new version of humanizer would have a lot of errors in there builds). Maybe you should look for another issue.
Mehdi Khalili
@MehdiK
I closed the extension method collision issue. It would be a huge breaking change as pointed out in FluentAssertions /cc @MaStr11 @ilanosortap
@ilanosortap may I suggest you familiarise yourself with the library first? You can read the code, build the solution, change the code to see what fails, break and fix a few tests, build simple sample projects using it etc. If you come across something you don't understand, please reach out here. Once you feel more comfortable with the codebase, pick up one of the issues, give it your best shot, send a PR (even if incomplete), and we'll be able to help you better that way.
Joachim Brehmer
@J-F-B-M

Hi, how would I change the outputted GrammaticalCase of a TimeSpan.Humanize()?
In german, 1.Weeks().Humanize() => "Eine Woche", but I'd prefer "einer Woche" (especially mind the extra r)

I want to write "in one week"/"in einer Woche", but at the current stage "in "+1.Weeks().Humanize() doesn't work, and any GrammaticalCase-Methods are for DateTime, not TimeSpan.
For now I handle this special case in-situ, as any higher number of weeks is a number, but this will break as soon as want to include more languages than English and German.

Obviously, in the actual case I use a computed TimeSpan which can have any length, but the Tests only break on 1.Weeks()
Martin Strecker
@MaStr11
@J-F-B-M German grammar for a timespan is incredible hard to get right (you have to take Nominativ, Genitiv, Dativ and Akkusativ into account: ein Tag, im Verlauf eines Tages, in einem Tag, im ersten Tag der Woche). I think it is reasonable to open an issue for this.
Joachim Brehmer
@J-F-B-M
Okay, thank you.
Joachim Brehmer
@J-F-B-M

While we are at it, (1) can I communicate to Humanizer that I want the number small (eine Woche instead of Eine Woche) and (2) can I specify a TimeUnit that is rounded up to (1.Minute().Humanize(atLeast: TimeUnit.Day) => "One day")?

For the former I transform it manually to a lowercase-number.
For the later I currently use new TimeSpan(Math.Max(myTimeSpan.Ticks, 1.Days().Ticks)).Humanize(), which is a bit unwieldy in the long run.

Martin Strecker
@MaStr11
Joachim Brehmer
@J-F-B-M

As the test shows TimeSpan.FromMilliseconds(10).Humanize(minUnit: <Anything higher than ms>) returns no time. But there is some time in the TimeSpan, that I want to round to the nearest day (in my case). minUnit doesn't achieve that. The only way so far seems to do the rounding manually beforehand.

I see the thought behind minUnit->no time, but I would like to know if an atLeast- or roundUpTo- construct is on-topic for this project or if I'm better off doing it all by myself.

Martin Strecker
@MaStr11
There isn't an issue for this request, so you may open one. The closest I could find is this #648.
Matteo
@Franklin89
Hi all, quick question...I want to use the ToQuantity method. What is the best way if I need it in for different localization? Do I first translate the string and then run the ToQuantity?
or the other way around? first ToQuantity and then translate?
cliff v
@powerdude
hi all. How do i use Titleize(), but keep hyphenated words in result?
Bluscream
@Bluscream
Hello