Comments (2)
Imagine some plugin interferes with effect name. Having prop accidentally overlap with effect would set that plugin. If plugin was enabled somewhere up dep chain, the user code can unexpectedly create collision, hard to debug.
But logically effects are on the same level as props <div html=${} foo bar=baz/>
.
That's a bit weird though - <div use=${( $el => $el.css )} css=${123} />
- is $el.css
prop here or effect? Seems that we have to display warning in case of collision.
Some external plugin cannot break code - but it can create errors for some existing code. Not really good.
from spect.
Some attrs are linked to props already, href
for example, and back.
Therefore $a.attr.href
=== $a.prop.href
.
If we provide direct props as $el.someProp
- should that forward all other props like $el.innerHTML
? That is more serious threat to namespace conflict. Also that contaminates the whole props concept - exposing meaningful wrappers to main domains.
Can we subset exposed props via html
? <a is=${NavA} href=/ foo=bar />
? So only props rendered via html
are exposed, or set directly on element $a.foo = 'bar'
. But should that then be reflected on DOM elements? $a.foo = 'bar'
- that's unexpected to assign that to all underneath elements. $a.prop.foo = 'bar'
is ok.
But
$a.html`<${NavLink} foo=bar route=/ ></>`
function NavLink({prop: {foo, route}}) {
// isn't 100% elegant
}
Should custom element function be a special aspect, receiving not wrapped element, but props?
No, because aspects may need to receive props as well.
Although, mb exposing domains like that is actually useful.
function SomeComponent ({ data: {foo, bar}, attr: {href}, prop: {route}, css: { width }}) {}
// vs
function SomeComponent ({ foo, bar, href, route, widht }) {}
it makes clear which domain a prop has come from.
Ok, sufficient proof for
Use domain-namespaced props, not direct props - that's easier to implement, less conflicts and more apparent to users.
from spect.
Related Issues (20)
- h: cache element by stack instead of creating anew HOT 1
- h: drop parser, use htm HOT 2
- v β f, v. Shaving off API, v as proxy HOT 6
- operators HOT 1
- 0b HOT 1
- v ~~as proxy~~ as observable HOT 1
- v: access multiarg values as [0], [1] etc. HOT 1
- $ β selector-collection HOT 2
- h: keyed. Why not morphing? HOT 3
- v(v0, v1, v2) - observables as args HOT 1
- $: pseudos? HOT 1
- h/$ - a nice way to convert data to template? HOT 2
- add Github Corner to spect.ly and fix typo HOT 2
- v23: animevents-only $ HOT 1
- 23.0: API reconsiderations, half-a-year later
- $: stop infinite recursion HOT 1
- $: first run flickers
- $(parent, β> childβ)
- h: lists; diff algo is underused. Possible syntax HOT 1
- spect@24 breaks integration tests with subscribable-things HOT 5
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 spect.