-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docs for different h()
algorithms
#9
Comments
This is all true, but that’s exactly why this project is here: the deal with all those changes. You can find out about how they work, by reading their docs. This project just supports all their interfaces, but it’s not this project’s place to document those projects? 🤔 I’m not sure what you suggest to do, and I feel like this is not the place, so closing for now. |
It was not about documenting those projects, but about documenting hastscript. Another projects is just an example of inconsistent behaviour. To be more clear, these things are not covered in hastscript docs and require experimenting and reading sources :
|
Oh whoops, I thought this issue was reported on To find out more about all your points above, please click through to HAST, it’s a really well defined specification. It answers all your points. I also remember there being a project to spec and stabilise all the different hyperscript-like interfaces, but can’t find it anymore unfortunately :( |
There is an attempt to standardise hyperscript hyperhype/hyperscript#66 but it went nowhere. Thanks, I'll check it out there. |
Yeah I think there was some other repo as well, but I can’t find it anymore :( |
There is no consistency with
h()
behavoiur:attributes
for attribues (and requires them to be kebab-case).attrs
for the same puprpose.And all of them does not document anything. Actual behaviour is salvaged from experiment and issues.
It would be really nice if hastscript would document what is actual format of
h()
arguments. Sorry if I'm missing something and this all is false.The text was updated successfully, but these errors were encountered: