You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, @louthy sorry if the discussion and PR were an overeach and sorry if the notifications of the PRs were bothering. All of the points you said all completedly valid and I will learn from them. Thanks :)
Also, by using "we" I didn't mean to include you, I was using using that word because it seams more professional, I'm so sorry for that. I understand that you're now on rest for a burnout. so please don't reply unless you feel okay
How we can grow the domain-traits of the library?
As you said, I understand the way I approch this may not be suited to the philosofy of Language-Ext, so first, is there a path where we can grow this module?
I get that the approch that I have is too opinionated and not precise, so I would like to know if there is anything that I code that would be a candidate to be in Language-Ext (Even if the answer is "nothing)
As I said before, the core idea was to create 3 main segments:
Easier definition of domain types and how they relate
Reusable and composable domain invariances
Separate how representation and creation of domain type
I will not ask you to search the code, I think it is too much. But I think that if you see a valid path for evolution, I can put my ideas together in a more light-weight form and show it to you. Anything that doesn't sound like Language-Ext won't appear, probably I'll add them to my framework
Thanks for your time and sorry por any inconvenience :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
First of all, @louthy sorry if the discussion and PR were an overeach and sorry if the notifications of the PRs were bothering. All of the points you said all completedly valid and I will learn from them. Thanks :)
Also, by using "we" I didn't mean to include you, I was using using that word because it seams more professional, I'm so sorry for that. I understand that you're now on rest for a burnout. so please don't reply unless you feel okay
How we can grow the domain-traits of the library?
As you said, I understand the way I approch this may not be suited to the philosofy of Language-Ext, so first, is there a path where we can grow this module?
I get that the approch that I have is too opinionated and not precise, so I would like to know if there is anything that I code that would be a candidate to be in Language-Ext (Even if the answer is "nothing)
As I said before, the core idea was to create 3 main segments:
I will not ask you to search the code, I think it is too much. But I think that if you see a valid path for evolution, I can put my ideas together in a more light-weight form and show it to you. Anything that doesn't sound like Language-Ext won't appear, probably I'll add them to my framework
Thanks for your time and sorry por any inconvenience :)
Beta Was this translation helpful? Give feedback.
All reactions