Skip to content

Commit

Permalink
make @app and @page work without using
Browse files Browse the repository at this point in the history
  • Loading branch information
@hhaensel
hhaensel committed Apr 9, 2024
1 parent 81dd7e6 commit 7a9bb03
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions src/ReactiveTools.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -77,12 +77,12 @@ function DEFAULT_LAYOUT(; title::String = "Genie App",
<div class='container'>
<div class='row'>
<div class='col-12'>
<% page(model, partial = true, v__cloak = true, [@yield], @iif(:isready)) %>
<% Stipple.page(model, partial = true, v__cloak = true, [Stipple.Genie.Renderer.Html.@yield], Stipple.@if(:isready)) %>
</div>
</div>
</div>
<% if isfile(joinpath(Genie.config.server_document_root, "js", "genieapp.js")) %>
<script src='$(Genie.Configuration.basepath())/js/genieapp.js'></script>
<script src='$(Stipple.Genie.Configuration.basepath())/js/genieapp.js'></script>
<% else %>
<% end %>
<footer class='_genie container'>
Expand Down Expand Up @@ -478,7 +478,7 @@ macro app(expr)
quote
$expr

@handlers
Stipple.ReactiveTools.@handlers
end |> esc
end

Expand Down Expand Up @@ -1181,7 +1181,7 @@ macro page(expressions...)
end

# modify the entry of the :model keyword by an init function with respective init_kwargs
model_parent[model_ind] = :($(Expr(:kw, :model, () -> @eval(__module__, @init($(init_kwargs...))))))
model_parent[model_ind] = :($(Expr(:kw, :model, () -> @eval(__module__, Stipple.ReactiveTools.@init($(init_kwargs...))))))
else
nothing
end
Expand Down

2 comments on commit 7a9bb03

@hhaensel
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/104534

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.28.8 -m "<description of version>" 7a9bb03705cc546cad086b64e63e0905d0329cb5
git push origin v0.28.8

Please sign in to comment.