-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
5b0a336
commit 20dc61b
Showing
1 changed file
with
38 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# Release Notes | ||
|
||
## 0.4.0-rc.1 | ||
|
||
This release candidate represents a major refactor of our client networking layer in LVN Core. | ||
It also changes how we encode stylesheets, from Elixir literals to JSON. | ||
|
||
The other major change is that all LVN related function components now *must* have arity of 2. | ||
For example, if you previously had function components in a render component such as: | ||
|
||
```elixir | ||
def clock(assigns) do | ||
~LVN""" | ||
<Clock time={@time} /> | ||
""" | ||
end | ||
``` | ||
|
||
it must now be changed to: | ||
|
||
```elixir | ||
def clock(assigns, _interface) do | ||
~LVN""" | ||
<Clock time={@time} /> | ||
""" | ||
end | ||
``` | ||
|
||
This aligns with the `render/2` in LVN render components but also it allows for granular conditionals within function components. | ||
|
||
You will need to update the `CoreComponents` file for your client so that all function components respond to arity of 2. Compilation will | ||
fail if there are any function components intended for LVN templates still using arity 1. | ||
|
||
### Known issues | ||
|
||
The SwiftUI client *will* fail to compile in Xcode 16.3 beta. The `SDKROOT` environment variable, which has been in Xcode for over 25 years, | ||
was removed in that beta relase with no explanation as to why or what should be used instead. We are working to resolve this for the upcoming | ||
release of Xcode. |