Comments (10)
I think such a separation and refactoring of the code base makes a lot of sense, @goofballLogic. I'm a strong proponent of having a core domain model completely dependency-free and only consisting of idiomatic C# code and having ancillary projects building and extending the core with references and dependencies to the outside world as per hexagonal architecture, onion architecture, clean architecture, etc.
from json-ld.net.
I guess because #80 was only merged yesterday, @goofballLogic.
from json-ld.net.
4.6 seems a fair sensible baseline. v1.0.6 (which is the version on NuGet) targets .Net Standard 1.3, and .Net framework 4.0 and 4.5 (with different profiles).
from json-ld.net.
I assume that v1.0.6 was either published to NuGet manually or there used to be a CI pipeline setup somewhere outside of GitHub. The build script does not appear to push to NuGet, nor do the GitHub actions thare are currently configured unless I'm missing something.
from json-ld.net.
I propose that given the nature of this library which should aim to support the lowest version of .NET standard across all the different platforms.
What does that mean, practically? Personally I think we can yank it up to .NET Standard 2.0, since that still supports all platforms. That would be a breaking change requiring a major version bump, though.
The build script does not appear to push to NuGet, nor do the GitHub actions thare are currently configured unless I'm missing something.
I've started a new CI/CD pipeline in #58. I can describe within it how I picture the build process is going to look like.
from json-ld.net.
Given that this library aims to be the go-to library for JSON-LD in .Net, is it worth attempting to retain compatibility with .NET Standard 1.0 for the algorithms themselves? We could then support enhanced versions of the API which can optionally be installed to allow for integration with Json.NET and/or System.Text.Json (.NET Core 3+).
Something like this perhaps:
+--------------------------+
| |
JObject-based API | json-ld.newtonsoft.net +----+
| | | +---------------+
+--------------------------+ | | |
+----> json-ld.net | string-based API and implementation
+--------------------------+ | | |
| | | +---------------+
System.Text.Json | json-ld.system.net +----+
-based API | |
+--------------------------+
from json-ld.net.
The other thing that might be worth considering is better support for DI. I know that the static classes provided are probably a good design decision for implementing the (basically stateless) JSON-LD algorithms, but it might be nice to provide an interface-based implementation to help when people would like to inject the library into their code in such a way that it can be mocked for unit testing, shimmed and decorated etc.
from json-ld.net.
100% agreed, @goofballLogic. Static, state- and side-effect-free methods make sense in a functional language, but in C# where DI containers are prevalent, immutability is difficult to guarantee and (shared) state is almost impossible to get rid of, I think an interface-based approach both sits better with the language and makes for a much more testable, readable, intuitive and robust codebase.
from json-ld.net.
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.
from json-ld.net.
Hmm. why did stale bot mark this as stale @asbjornu ? It is on a milestone.
from json-ld.net.
Related Issues (20)
- Rename `master` to `main`
- Version 1.0.7 is missing on nuget.org HOT 7
- @embed not supported? HOT 2
- Microsoft.Bcl.Async is deprecated HOT 2
- JsonLdProcessor.Frame(...): poor performance on large sets of objects HOT 2
- Release 1.0.6 HOT 1
- Strong name sign json-ld.net assemblies HOT 7
- Control order of graph nodes and children nodes HOT 1
- Getting OutOfMemoryError while try to frame JsonLd HOT 3
- Replace Travis with GitHub Actions HOT 1
- Evolve or Rewrite? HOT 13
- Support dependency-free API HOT 16
- Support dependency-injection HOT 3
- Support System.Text.Json HOT 2
- Add Markdown guidelines
- Support for signing HOT 9
- Reduce public API to a bare minimum HOT 3
- Add LINQPad NuGet samples HOT 4
- API advertised in documentation/samples is now `internal` HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from json-ld.net.