2021-05-01 23:02:08 +02:00
|
|
|
require "./shards"
|
|
|
|
|
|
|
|
|
|
Lucky::AssetHelpers.load_manifest
|
|
|
|
|
|
|
|
|
|
require "./app_database"
|
First step rendering a page
The API responds with a bunch of paragraphs which the client converts
into Paragraph objects.
This turns the paragraphs in a PostResponse's Paragraph objects into the
form needed to render them on a page. This includes converting flat list
elements into list elements nested by a UL. And adding a limited markups
along the way.
The array of paragraphs is passed to a recursive function. The function
takes the first paragraph and either wraps the (marked up) contents in a
container tag (like Paragraph or Heading3), and then moves onto the next
tag. If it finds a list, it starts parsing the next paragraphs as a list
instead.
Originally, this was implemented like so:
```crystal
paragraph = paragraphs.shift
if list?
convert_list([paragraph] + paragraphs)
end
```
However, passing the `paragraphs` after adding it to the already shifted
`paragraph` creates a new object. This means `paragraphs` won't be
mutated and once the list is parsed, it starts with the next element of
the list. Instead, the element is `shift`ed inside each converter.
```crystal
if paragraphs.first == list?
convert_list(paragraphs)
end
def convert_list(paragraphs)
paragraph = paragraphs.shift
# ...
end
```
When rendering, there is an Empty and Container object. These represent
a kind of "null object" for both leafs and parent objects respectively.
They should never actually render. Emptys are filtered out, and
Containers are never created explicitly but this will make the types
pass.
IFrames are a bit of a special case. Each IFrame has custom data on it
that this system would need to be aware of. For now, instead of trying
to parse the seemingly large number of iframe variations and dealing
with embedded iframe problems, this will just keep track of the source
page URL and send the user there with a link.
2021-05-16 20:14:25 +02:00
|
|
|
require "./constants"
|
2021-05-01 23:02:08 +02:00
|
|
|
require "./models/base_model"
|
|
|
|
|
require "./models/mixins/**"
|
|
|
|
|
require "./models/**"
|
|
|
|
|
require "./queries/mixins/**"
|
|
|
|
|
require "./queries/**"
|
|
|
|
|
require "./operations/mixins/**"
|
|
|
|
|
require "./operations/**"
|
|
|
|
|
require "./serializers/base_serializer"
|
|
|
|
|
require "./serializers/**"
|
|
|
|
|
require "./actions/mixins/**"
|
|
|
|
|
require "./actions/**"
|
|
|
|
|
require "./components/base_component"
|
|
|
|
|
require "./components/**"
|
First step rendering a page
The API responds with a bunch of paragraphs which the client converts
into Paragraph objects.
This turns the paragraphs in a PostResponse's Paragraph objects into the
form needed to render them on a page. This includes converting flat list
elements into list elements nested by a UL. And adding a limited markups
along the way.
The array of paragraphs is passed to a recursive function. The function
takes the first paragraph and either wraps the (marked up) contents in a
container tag (like Paragraph or Heading3), and then moves onto the next
tag. If it finds a list, it starts parsing the next paragraphs as a list
instead.
Originally, this was implemented like so:
```crystal
paragraph = paragraphs.shift
if list?
convert_list([paragraph] + paragraphs)
end
```
However, passing the `paragraphs` after adding it to the already shifted
`paragraph` creates a new object. This means `paragraphs` won't be
mutated and once the list is parsed, it starts with the next element of
the list. Instead, the element is `shift`ed inside each converter.
```crystal
if paragraphs.first == list?
convert_list(paragraphs)
end
def convert_list(paragraphs)
paragraph = paragraphs.shift
# ...
end
```
When rendering, there is an Empty and Container object. These represent
a kind of "null object" for both leafs and parent objects respectively.
They should never actually render. Emptys are filtered out, and
Containers are never created explicitly but this will make the types
pass.
IFrames are a bit of a special case. Each IFrame has custom data on it
that this system would need to be aware of. For now, instead of trying
to parse the seemingly large number of iframe variations and dealing
with embedded iframe problems, this will just keep track of the source
page URL and send the user there with a link.
2021-05-16 20:14:25 +02:00
|
|
|
require "./classes/**"
|
|
|
|
|
require "./clients/**"
|
2021-05-01 23:02:08 +02:00
|
|
|
require "./pages/**"
|
|
|
|
|
require "../config/env"
|
|
|
|
|
require "../config/**"
|
|
|
|
|
require "../db/migrations/**"
|
|
|
|
|
require "./app_server"
|