Skip to content

Commit fc8197f

Browse files
authored
Merge pull request #43 from jbampton/fix-spelling
Fix spelling
2 parents 308cee3 + f2e01c7 commit fc8197f

File tree

4 files changed

+8
-8
lines changed

4 files changed

+8
-8
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,8 @@ julia> run_server(app, "0.0.0.0", 8080)
5858
* The `DashApp` struct represents a dashboard application.
5959
* To make `DashApp` struct use `dash(layout_maker::Function, name::String; external_stylesheets::Vector{String} = Vector{String}(), url_base_pathname="/", assets_folder::String = "assets")`` where `layout_maker` is a function with signature ()::Component
6060
* Unlike the Python version where each Dash component is represented as a separate class, all components in Dash.jl are represented by struct `Component`.
61-
* You can create `Component` specific for concrete Dash component by the set of functions in the form ``lowercase(<component package>)_lowercase(<component name>)``. For example, in Python html `<div>` element is represented as `HTML.Div` in Dasboards it is created using function `html_div`
62-
* The list of all supported components is available in docstring for Dasboards module.
61+
* You can create `Component` specific for concrete Dash component by the set of functions in the form ``lowercase(<component package>)_lowercase(<component name>)``. For example, in Python html `<div>` element is represented as `HTML.Div` in Dashboards it is created using function `html_div`
62+
* The list of all supported components is available in docstring for Dashboards module.
6363
* All functions for a component creation have the signature `(;kwargs...)::Component`. List of key arguments specific for the concrete component is available in the docstring for each function.
6464
* Functions for creation components which have `children` property have two additional methods ``(children::Any; kwargs...)::Component`` and ``(children_maker::Function; kwargs..)::Component``. `children` must by string or number or single component or collection of components.
6565
* ``make_handler(app::Dash; debug::Bool = false)`` makes a handler function for using in HTTP package.
@@ -112,7 +112,7 @@ end
112112
julia> run_server(app, "0.0.0.0", 8080)
113113
```
114114

115-
## Comparation with original Python syntax
115+
## Comparision with original Python syntax
116116

117117
### component naming:
118118

docs/src/index.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -55,8 +55,8 @@ julia> HTTP.serve(handler, HTTP.Sockets.localhost, 8080)
5555
* The `Dash` struct represent dashboard application.
5656
* The constructor for `Dash` struct is ``Dash(layout_maker::Function, name::String; external_stylesheets::Vector{String} = Vector{String}(), url_base_pathname="/", assets_folder::String = "assets")`` where `layout_maker` is a function with signature ()::Component
5757
* Unlike the python version where each Dash component is represented as a separate class, all components in Dashboard are represented by struct `Component`.
58-
* You can create `Component` specific for concrete Dash component by the set of functions in the form ``lowercase(<component package>)_lowercase(<component name>)``. For example, in python html `<div>` element is represented as `HTML.Div` in Dasboards it is created using function `html_div`
59-
* The list of all supported components is available in docstring for Dasboards module
58+
* You can create `Component` specific for concrete Dash component by the set of functions in the form ``lowercase(<component package>)_lowercase(<component name>)``. For example, in python html `<div>` element is represented as `HTML.Div` in Dashboards it is created using function `html_div`
59+
* The list of all supported components is available in docstring for Dashboards module
6060
* All functions for a component creation have the signature `(;kwargs...)::Component`. List of key arguments specific for the concrete component is available in the docstring for each function
6161
* Functions for creation components which have `children` property have two additional methods ``(children::Any; kwargs...)::Component`` and ``(children_maker::Function; kwargs..)::Component``. `children` must by string or number or single component or collection of components
6262
* ``make_handler(app::Dash; debug::Bool = false)`` makes handler function for using in HTTP package
@@ -105,7 +105,7 @@ julia> HTTP.serve(handler, HTTP.Sockets.localhost, 8080)
105105
```
106106
* For multiple output callback must return any collection with element for each output
107107

108-
## Comparation with original python syntax
108+
## Comparision with original python syntax
109109

110110
### component naming:
111111

src/Front.jl

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,6 @@ function from_dash(::Type{PlotlyBase.Plot}, t)
1212
PlotlyBase.Plot(data, layout)
1313
end
1414

15-
#FIXME It's not elegant, but I didn't find elegant soluiton
15+
#FIXME It's not elegant, but I didn't find elegant solution
1616
JSON2.write(io::IO, p::PlotlyBase.Plot; kwargs...) = write(io, JSON.json(p))
1717
end

src/config.jl

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
function absolute_assets_path(assets_path::AbstractString)
2-
#TODO app path, enviroment variable etc..
2+
#TODO app path, environment variable etc..
33
return joinpath(pwd(), assets_path)
44
end
55

0 commit comments

Comments
 (0)