Comments (4)
In atomic-cli
, I've implemented logic to deal with who's the current Agent, and where the Server is located which should be writed to. However, I think this kind of logic (dealing with who's the agent and where the server is located) should sit in Store
, and be tucked away as much as possible. Store
should know the default Agent and the Server's address. This should prevent explicitly passing things like the Agent's private key, the server's URL and more to all sorts of functions.
from atomic-server.
Resource.save()
is one of the methods that needs to know: 'should I post this commit, before I apply it locally, or am I the source of truth?'
from atomic-server.
I've ran into an issue with this. The client used get_base_url
to determine if a resource should be present. This made sense in the server, but not in the client. I ended up adding a get_self_url
function, which returns Option<url>
. Currently, only DB returns a value, since that is used in server. Not sure how this should work in the end, I'm not quite happy with the current state, but it works.
from atomic-server.
Also had to add save_locally
(especially for quick tests)
from atomic-server.
Related Issues (20)
- Add JS CLI docs to docs
- Creating relations between classes in ontology editor can be simplified
- Auto-renew TLS requires reboot, takes too long HOT 2
- CSS weird long content in LineRow
- Explore replacing @tomic/cli with generating packages on the server HOT 1
- Docs improvements
- Drive not properly saved after accepting invite
- Add `Website` Class and View (replaces `ArguSite`) HOT 2
- Move localstorage logic from @tomic/react to databrowser
- File resource doesn't support CJK file name HOT 2
- CI should fail if E2E fails
- Support for non-tag resource arrays in Tables
- URL encoding bug: "Incorrect signature" when creating resources with special characters in URL
- Forms - submit-only view
- Sidebar shifts a few pixels when navigating
- New Version Changelog Screen HOT 1
- Regular pipeline should not update docs / push things
- browser+test fails in CI HOT 1
- CLI tool to update/create hardcoded json-ad data from ontologies
- Chinese / Japanese / Korean tokenizer support for search / tantivy HOT 2
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 atomic-server.