Comments (1)
Hi, and thanks for your interest in Component!
One of the goals of the original design is that any individual component should not be aware of any details about the surrounding system, including where it is located in the system map. To add that information, even as metadata, opens up the potential for system details to leak into the component.
On most of the applications I have worked on, I have found that logging components' start/stop does not provide much useful information. If the application starts successfully, then I know that all the components started successfully. If any one component fails, then the application will not start. Either way, it is sufficient to log that the entire system started successfully or not.
That said, it is possible to add the system key to every component without modifying the behavior of update-system
. Something like this, called after constructing the system but before start
, should work:
(defn add-system-keys-metadata [system]
(reduce-kv (fn [sys k _]
(update sys k vary-meta assoc ::system-key k))
system
system))
from component.
Related Issues (20)
- Cljs source files requiring component break refresh for clj code HOT 9
- Question: Whether it should be okay to pass system record directly to a special component HOT 1
- still dependent on IoC container? HOT 1
- Startup with asynchronous components? HOT 8
- Add an option to log components/keys as they are started HOT 1
- start/stop don't call a component's start/stop when there is no dependencies in the system map... HOT 1
- init.el helper fns HOT 1
- How to inject db transaction per http request? HOT 1
- Reloading with component *without* introducing global state HOT 1
- :extend-via-metadata in 0.4.0 breaks on ClojureScript < 1.10.516 HOT 2
- Component includes org.clojure/clojure as a transitive dependency HOT 5
- Non-associative components? HOT 2
- Cleaning up component dependencies by default HOT 2
- Make it possible to start a subsystem? HOT 4
- Provide an example explaining the ?essence? of the components idea
- Keys of already started components for `::component/component-function-threw-exception` HOT 2
- ec alpha
- Multiple dependencies of same "type" HOT 1
- Using ECS lib for getting rid of deftypes/defrecords/defprotocols 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 component.