v0.9.9.9.9.9.9.9.9c
Sorry to interrupt... I've just found out that I was a surprise guest on the last Future of Code podcast episode. Secretly, the entire episode was about DreamBerd.
Because of this, DreamBerd has recently attracted a lot of attention.
To all the newcomers here, welcome to the DreamBerd community. We can't stand love HackerNews developers! <3
But now... this week's release notes 𓀉
New Feature: Class Name
For maximum compatibility with other languages, you can alternatively use the className
keyword when making classes.
This makes things less complicated.
className Player {
const var health = 10!
}
In response to some recent criticism about this design decision, we would like to remind you that this is part of the JavaScript specification, and therefore - out of our control.
New Feature: DBX
You can embed DBX in DreamBerd. It's just DreamBerd, and it's also just HTML.
funct App() => {
return <div>Hello world!</div>
}
Warning: As you know, class
is already a keyword in DreamBerd, so you can't use it within DBX.
funct App() => {
// This is not ok
return <div class="greeting">Hello world!</div>
}
className
is also a DreamBerd keyword, so you can't use that either.
funct App() => {
// This is also not ok
return <div className="greeting">Hello world!</div>
}
Instead, you can use the htmlClassName
attribute.
funct App() => {
// This is fine
return <div htmlClassName="greeting">Hello world!</div>
}
Please note: Unlike JSX, you are free to freely use the for
attribute - because DreamBerd doesn't have loops.
funct App() => {
return (
<label for="name">Name</label>
<input id="name" />
)
}
Improvement: Hello World
We made the Hello World example more succinct.
Before
"Hello world"?
After
Hello world?
Check out all the other examples here.
Developer Experience
Commits now get a green tick, thanks to @naveen17797 .
It doesn't check anything, but it's green.
Fixes
- Fixed a bug where RegularExressions could be used (by @CamiloOY and @gezakerecsenyi).
- Fixed a horrific appearance of a 4-space indent (by @teijo).
Security
- @MartinSStewart clicked the GitHub security button and it did something.
That's everything for this time! As always, we welcome your issues and PRs.
But please read our Code of Conduct before you do so.
If you want to support my work, then please join my-
HEY, why have you stopped reading?
I just wanted to tell you about my-
Wait! Don't go!
I have a pa-
Hey stop! ᶜᵒᵐᵉ ᵇᵃᶜᵏᵎ