Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 30 04:01
    Build #15 passed
  • Oct 30 04:00
    Starfire1853 opened #208
  • Aug 18 23:04
    danieljsummers opened #6
  • Dec 29 2018 04:30
    panesofglass commented #195
  • Dec 29 2018 04:29
    panesofglass commented #195
  • Dec 29 2018 04:27
    panesofglass closed #198
  • Dec 29 2018 04:27
    panesofglass commented #198
  • Dec 29 2018 04:26
    panesofglass labeled #200
  • Dec 29 2018 04:26
    panesofglass labeled #200
  • Dec 29 2018 04:26
    panesofglass labeled #206
  • Dec 29 2018 04:25
    panesofglass labeled #207
  • Dec 29 2018 04:25
    panesofglass labeled #207
  • Dec 29 2018 04:25
    panesofglass labeled #207
  • Dec 29 2018 04:25
    panesofglass labeled #207
  • Dec 29 2018 04:25
    panesofglass opened #207
  • Dec 28 2018 22:30
    panesofglass edited #206
  • Dec 28 2018 22:29
    panesofglass edited #206
  • Dec 28 2018 22:10
    panesofglass edited #206
  • Dec 28 2018 22:08
    panesofglass opened #206
  • Oct 31 2018 15:30
    et1975 edited #205
Ryan Riley
@panesofglass
If only net461 and above actually consumed netstandard2.0 as was originally described, we could probably drop net45.
Pete Johanson
@petejohanson
Ah, that makes sense.
Pete Johanson
@petejohanson
Bummer.
Ryan Riley
@panesofglass
Apparently, the guidance on twitter doesn't match what's published, and there's some debate about how to resolve it: dotnet/docs#7305
Pete Johanson
@petejohanson
Sounds like to be safe, Freya still needs to package net45 compiles as well.
Ryan Riley
@panesofglass
I've got everything updated to netstandard2.0. I need to start publishing packages, which I'll do likely after Open FSharp, given time constraints. Expect releases on NuGet within a few weeks. :D
Florian Verdonck
@nojaf
Great news, thanks for your efforts
Andrew Cherry
@kolektiv
Awesome stuff @panesofglass :)
Ryan Riley
@panesofglass
It's taking me a bit longer than I'd like, but I'm steadily making progress on releases. With the help of @ninjarobot and @ctaggart, I've gotten updated builds for Aether, Anat, and Chiron (v6) released.
I'm working up to the others. These have to go out first so that I can move the Freya libraries off of @neoeinstein's myget feed.
Also, @kolektiv, if you add export FrameworkPathOverride=$(dirname $(which mono))/../lib/mono/4.5/to your .bash_profile and restart your terminal, you'll find you can build successfully even with a net45(2) target. This is assuming you also have installed the mono-mdk with brew cask install mono-mdk.
Ryan Riley
@panesofglass
I've further installed PowerShell Core as described here: https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-macos?view=powershell-6 so that I can just run the build.ps1 rather than the dotnet cli commands directly, but both should work. I'm happy to add a convenience build.sh if someone wants it.
Or that may make a great and easy PR
Lastly, travis builds are beginning to run to verify this stuff builds well on a Mac or Linux machine. You can always look there for guidance.
Pete Johanson
@petejohanson
I'm curious if other are interested, but using Gitlab CI, I also had auto release of nugets for tags working... Might help reduce maintainer effort as well.
(I've made some progress on trying to rebase/cherry-pick my feature changes to things like freya-types to be able to create PRs, but nothing quite ready)
Ryan Riley
@panesofglass
:+1:
Pete Johanson
@petejohanson
Note: To get the net45 stuff working that way would require the same FrameworkPathOverride hack, not sure if the produced DLLs for that target when built by Mono instead of MS .NET Framework are acceptable or not.
Ryan Riley
@panesofglass
I've made it through most of Freya at this point with v4.0.0 releases. I still have machines, the meta package, and template(s) to go, as well as updating examples, which is likely a lot more work.
Ryan Riley
@panesofglass
All libraries are updated. Only the template remains!
Andrew Cherry
@kolektiv
That's awesome! I'm not sure how much work there'd be on the examples either - I think most of them were semi-up-to-date? But I could be completely misremembering... Either way, fantastic work @panesofglass, and everyone such as @ninjarobot and @ctaggart that helped!
Ryan Riley
@panesofglass
Thanks, @kolektiv! By the way, how do I register the new template, which is now updated?
Ryan Riley
@panesofglass
I think I figured it out
@kolektiv I need permission to push to freya-template. Can you grant me that?
on nuget, that is
nm; looks like my nuget key was just insufficient
Ryan Riley
@panesofglass
Freya.Template is published!
Ryan Riley
@panesofglass
As I recall, the TodoBackend example never quite worked, and it appears it still does not. Anyone want to help with that?
Anyone have any opinions on xyncro/freya#200 now that 4.0 is released?
btrepp
@btrepp
Awesome work ryan!
Andrew Cherry
@kolektiv
when you say the TodoBackend example never quite worked, how do you mean? I used to run it against the test suite fine...
Florian Verdonck
@nojaf
Any examples of returning a pdf with freya?
ShalokShalom
@ShalokShalom
hi there
I am interested in some idiomatic freya code
Daniel J. Summers
@danieljsummers
Howdy, y'all. I've reworked my "objects to functions" project for .NET Standard 2.0, and I'm to the point of trying to implement a session store for my Freya implementation. Are the .Http.State types and optics ready for prime time? I've tried a bit, but I'm not getting anywhere. I'm continuing to learn the optics way of doing things, so it may be me; but, before I go much further down the path I'm going, I wanted to find out if I'm working against a beta library.
I'm really just trying to read and set a simple session cookie with a session ID.
BTW, here's the new repo. https://github.com/bit-badger/o2f
Eugene Tolmachev
@et1975
@danieljsummers optics work, just fine, out of the box response options are limited however
You may want to look into w3c spec for cookies and work your way up from that
Daniel J. Summers
@danieljsummers
I've made some progress since my original question. It looks like the cookie_ lens is missing a parameter in the setter; its signature was Pair list -> Cookie, but to follow the pattern of other lenses, it should be Pair list -> Cookie -> Cookie. (That was the genesis of my original question.) I'll keep working on it and post back here if I run into a roadblock.
Are you aware of any samples I could review?
Eugene Tolmachev
@et1975
ah, sorry. No, not aware of any cookie samples.
Daniel J. Summers
@danieljsummers
I'm quite excited - I got the cookie stuff working! My session provider increments the counts just like the other 4!
The code is at https://github.com/bit-badger/o2f/tree/53e650b9fef8502cc8a862a8079e14e4d7d01bdb/src/5-Cinco - Sessions.fs has the cookie stuff and the RavenDB access, and Handlers.fs (for the hello handler) shows it using it to increment the count for the home page.
Now to write about it a bit... :)
Daniel J. Summers
@danieljsummers
I decided to break it out and make a more fully featured session provider (that encrypts the session cookie, among other things). I just released it a few minutes ago; the repo is https://github.com/bit-badger/FreyaSessionProvider .
The only implementation for now uses RavenDB, but I wrote it in such a way that I should be able to plug in whatever persistence mechanism we need, and just have to implement 4 data store actions to do it.
Florian Verdonck
@nojaf
V cci