craigchamberlain / solarlunardate Goto Github PK

Ref:  CS-215392-D0Y4  Your enquiry has been received and logged under this unique Reference Number, which should be quoted in any further correspondence with us.

Good afternoon Craig,

To obtain historical and future tides you can use our EasyTide service (http://www.ukho.gov.uk/easytide/EasyTide/index.aspx), please note though that while the current day and the next 6 days predictions are free, anything further in to the future or in the past can be accessed by purchasing vTickets - details are on the website.

I hope this helps.

Kind regards

Stephen Cooper 

Make clients threadsafe so they can be long lived and potentially attached the solarlunardate type so it can add dates and validate inputs.

https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters&WT.mc_id=-blog-scottha

Some help here:
https://www.hanselman.com/blog/automatic-unit-testing-in-net-core-plus-code-coverage-in-visual-studio-code
https://www.hanselman.com/blog/net-core-code-coverage-as-a-global-tool-with-coverlet
Consider writing update on blog.

Can be done directly in code, can be a bit verbose and needs recompiling for every change.

https://www.red-gate.com/simple-talk/dotnet/software-tools/documenting-your-powershell-binary-cmdlets/

Had some problems with this tool but it seems to have been developed recently
https://github.com/red-gate/XmlDoc2CmdletDoc

Have take a quick look at code climate and coverlet/coveralls

• Add a badge to readme and start using (CodeClimate)
• Setup and configure Coveralls
• Add a badge to readme and start using (Coveralls)

Cover Alls links
https://coveralls.io/
https://github.com/csmacnz/coveralls.net
https://github.com/csMACnz/coveralls.net/wiki
https://medium.com/@tonerdo/setting-up-coveralls-with-coverlet-for-a-net-core-project-2c8ec6c5dc58

The date picker @ https://craigchamberlain.github.io/SolarLunarDate/tool/ should have year selection.

Have asked fulma creator and suggested I fixed up the code and offered some advice

here is partial quote of response.

Hum, you would need to learn Fable interop and also look at how it can be done in pure JavaScript.

Fable interop guide (bit old but should still be a good read): https://medium.com/@zaid.naom/f-interop-with-javascript-in-fable-the-complete-guide-ccc5b896a59f
Fable interop guide #2: https://fable.io/docs/communicate/js-from-fable.html

If you don't want to it in pure F# you can also make the wrapper in JS and then interop with your wrapper

JavaScript wrapper: CopyButton.js
F# binding for it: https://github.com/MangelMaxime/html-to-elmish/blob/master/src/WebApp/App.fs#L87-L95

Have started learning some react but a long way of implementing this feature myself.

In F# there is the result and option type. In C# there is https://github.com/csMACnz/Beefeater

JsonTextReader() Should improve memory utilisation.

https://www.newtonsoft.com/json/help/html/Performance.htm#MemoryUsage

Look at how power shell gallery and nuget handle this.

https://jeffbrown.tech/getting-started-with-pester-testing-in-powershell/

https://pester.dev/

Had problems today raising date not found exception from a system IO exception. If I was using the remote client it would throw an exception on a 404 request.

Need to isolate a solution. Where can I perform tests for valid, year, month.

Consider Code Contracts to push exception handling into the interface of the clients?

https://www.selenium.dev/
https://www.cypress.io/

See RemoteJson.cs in standard project.

https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/

The test suite uses my client for this API. This client itself tests against the API in the integration stage.

Not enough unit tests exist. It it is to dependent of real data being provided, not mocked and returning desired result.

Want to alter the public api for major version,

For now mark in compiler:
https://stackoverflow.com/questions/1759352/how-to-mark-a-method-as-obsolete-or-deprecated

I currently have a script which generates and uploads the files. I currently run this locally. Don't think I can do with Travis, Do I start using AppVeyor. It seems .NET support for test coverage is coming to both CodeClimate and Travis.

Happy with running the tests locally in the short term should push to CI process or use a git action?

find . -path "*/TestResults/*" -exec rm "{}" -r \;

find . -path "*.Tests" -exec dotnet test --collect:"XPlat Code Coverage" "{}" -- DataCollectionRunSettings.DataCollectors.DataCollector.Configuration.Format=opencover  \;


COVERAGEFILES=""
for x in $(find . -path */coverage.opencover.xml); do
    COVERAGEFILES+="opencover=$x;"
done
COVERAGEFILES="$(sed -e 's/;$//' <<< $COVERAGEFILES)"

csmacnz.Coveralls \
  --multiple \
  -i $COVERAGEFILES \
  --commitId $(git log --format="%H" -n 1) \
  --commitBranch $(git rev-parse --abbrev-ref HEAD)