render-engine-json 0.0.0__tar.gz

render_engine_json-0.0.0/.devcontainer/devcontainer.json

@@ -0,0 +1,25 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/python
+{
+	"name": "Python 3",
+	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+	"image": "mcr.microsoft.com/devcontainers/python:0-3.11-bullseye",
+	"features": {
+		"ghcr.io/devcontainers/features/github-cli:1": {}
+	}
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+	// Configure tool-specific properties.
+	// "customizations": {},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

render_engine_json-0.0.0/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,108 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at kjaymiller@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

render_engine_json-0.0.0/.github/LICENSE.md

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2023 
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

render_engine_json-0.0.0/.github/workflows/publish.yml

@@ -0,0 +1,30 @@
+name: Build distribution
+
+on: 
+  release:
+    types: [created]
+
+jobs:
+  deploy:
+    name: Deploy to PyPI
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout source
+        uses: actions/checkout@v4
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v4
+        with:
+          python-version: 3.12
+
+      - name: Install build dependencies
+        run: python -m pip install build twine
+
+      - name: Build distributions
+        run: python -m build
+
+      - name: Publish package to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          user: __token__
+          password: ${{ secrets.TWINE_PASSWORD}}

render_engine_json-0.0.0/.gitignore

@@ -0,0 +1,162 @@
+/.vscode# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+.vscode

render_engine_json-0.0.0/.pre-commit-config.yaml

@@ -0,0 +1,26 @@
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.4.0
+    hooks:
+    -   id: check-yaml
+    -   id: end-of-file-fixer
+    -   id: trailing-whitespace
+-   repo: https://github.com/psf/black
+    rev: 22.12.0
+    hooks:
+    -   id: black
+-   repo: https://github.com/PyCQA/isort
+    rev: 5.11.4
+    hooks:
+    -   id: isort
+        args: ["--profile", "black"]
+# Add pip-compile to pre-commit hooks
+-   repo: https://github.com/jazzband/pip-tools
+    rev: 6.12.1
+    hooks:
+    -   id: pip-compile
+        name: pip-compile
+        args: ["--extra=dev", "--upgrade", "pyproject.toml"]
+    -   id: pip-compile
+        name: pip-compile
+        args: ["--extra=docs", "--upgrade", "pyproject.toml", "-o", "docs/requirements.txt"]

render_engine_json-0.0.0/.vscode/settings.json

@@ -0,0 +1,16 @@
+{
+    "workbench.colorCustomizations": {
+        "commandCenter.border": "#15202b99",
+        "statusBar.background": "#f9e64f",
+        "statusBar.foreground": "#15202b",
+        "statusBarItem.hoverBackground": "#f7df1e",
+        "statusBarItem.remoteBackground": "#f9e64f",
+        "statusBarItem.remoteForeground": "#15202b",
+        "titleBar.activeBackground": "#f9e64f",
+        "titleBar.activeForeground": "#15202b",
+        "titleBar.inactiveBackground": "#f9e64f99",
+        "titleBar.inactiveForeground": "#15202b99"
+    },
+    "peacock.color": "#f9e64f",
+    "peacock.remoteColor": "#832561"
+}

render_engine_json-0.0.0/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.1
+Name: render_engine_json
+Version: 0.0.0
+Summary: JSON Parser and Collection for Render Engine
+Project-URL: homepage, https://github.com/kjaymiller/render_engine_json/
+Project-URL: repository, https://github.com/kjaymiller/render_engine_json/
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: render-engine>=2023.12.1b3
+Requires-Dist: python-slugify
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+
+# Render Engine JSON
+
+JSON Parser and Collection Module for Render Engine
+
+## Installation
+
+```bash
+pip install render_engine_json
+```
+
+## Usage
+
+The `render-engine-json` extends render-engine to allow you to build pages and collections using JSON. 
+
+The `JSONPageParser` class can be used to parse a single JSON page and the `JSONCollection` class can be used to parse a single collection of JSON pages.
+
+> **NOTE**
+> The `JSONCollection` class is designed to work with a single JSON file that contains an array of JSON Objects or a JSON Hash where the keys are the slugs. If you want to work with multiple JSON files you can use a regular `Collection` and the `JSONPageParser` as the parser.
+
+### Single JSON Page Entry
+
+To create a json entry you will need the `JSONPageParser` class as the Parser for your `Page` Object.
+
+You can pass the page a json string or a json file path.
+
+#### As a string
+
+```python
+
+from render_engine import Page, Site
+from render_engine_json import JSONPageParser
+
+site = Site()
+
+json_page = """
+{
+    "title": "My JSON Page",
+    "content": "This is my json page"
+}
+"""
+
+@site.page
+class JSONStringPage(Page):
+    parser = JSONPageParser
+    content = json_page
+
+```
+
+#### As a file
+
+```python
+
+@site.page
+class JSONFilePage(Page):
+    parser = JSONPageParser
+    content_path = "path/to/json/file.json"
+
+```
+
+### JSON Collection
+
+To create a JSON collection you will need the `JSONCollection` Object.
+
+You can pass the collection a json string or a json file path.
+
+#### As a string
+
+```python
+from render_engine import Site, Collection
+from render_engine_json import JSONCollection, JSONPageParser
+
+site = Site()
+
+json_collection = """
+[
+    {
+        "title": "My JSON Page",
+        "content": "This is my json page"
+    },
+    {
+        "title": "My JSON Page 2",
+        "content": "This is my json page 2"
+    }
+]
+"""
+
+@site.collection
+class JSONStringCollection(Collection):
+    parser = JSONPageParser
+    content = json_collection
+
+```
+
+
+```

render_engine_json-0.0.0/README.md

@@ -0,0 +1,95 @@
+# Render Engine JSON
+
+JSON Parser and Collection Module for Render Engine
+
+## Installation
+
+```bash
+pip install render_engine_json
+```
+
+## Usage
+
+The `render-engine-json` extends render-engine to allow you to build pages and collections using JSON. 
+
+The `JSONPageParser` class can be used to parse a single JSON page and the `JSONCollection` class can be used to parse a single collection of JSON pages.
+
+> **NOTE**
+> The `JSONCollection` class is designed to work with a single JSON file that contains an array of JSON Objects or a JSON Hash where the keys are the slugs. If you want to work with multiple JSON files you can use a regular `Collection` and the `JSONPageParser` as the parser.
+
+### Single JSON Page Entry
+
+To create a json entry you will need the `JSONPageParser` class as the Parser for your `Page` Object.
+
+You can pass the page a json string or a json file path.
+
+#### As a string
+
+```python
+
+from render_engine import Page, Site
+from render_engine_json import JSONPageParser
+
+site = Site()
+
+json_page = """
+{
+    "title": "My JSON Page",
+    "content": "This is my json page"
+}
+"""
+
+@site.page
+class JSONStringPage(Page):
+    parser = JSONPageParser
+    content = json_page
+
+```
+
+#### As a file
+
+```python
+
+@site.page
+class JSONFilePage(Page):
+    parser = JSONPageParser
+    content_path = "path/to/json/file.json"
+
+```
+
+### JSON Collection
+
+To create a JSON collection you will need the `JSONCollection` Object.
+
+You can pass the collection a json string or a json file path.
+
+#### As a string
+
+```python
+from render_engine import Site, Collection
+from render_engine_json import JSONCollection, JSONPageParser
+
+site = Site()
+
+json_collection = """
+[
+    {
+        "title": "My JSON Page",
+        "content": "This is my json page"
+    },
+    {
+        "title": "My JSON Page 2",
+        "content": "This is my json page 2"
+    }
+]
+"""
+
+@site.collection
+class JSONStringCollection(Collection):
+    parser = JSONPageParser
+    content = json_collection
+
+```
+
+
+```

render_engine_json-0.0.0/pyproject.toml

@@ -0,0 +1,42 @@
+[build-system]
+requires = ["setuptools", "setuptools_scm", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "render_engine_json"
+dynamic = [ "version" ]
+description = "JSON Parser and Collection for Render Engine"
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "render-engine >= 2023.12.1b3",
+    "python-slugify"
+]
+
+
+[project.optional-dependencies]
+dev=[
+    "pytest"
+]
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+
+[project.urls]
+homepage = "https://github.com/kjaymiller/render_engine_json/"
+repository = "https://github.com/kjaymiller/render_engine_json/"
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]
+
+[tool.semantic_release]
+version_toml = "pyproject.toml:project.version"
+branch = "main"
+
+[tool.ruff]
+select = ["E", "F", "I", "UP"]
+target-version = "py311"
+line-length = 120
+src = ["src"]
+ignore-init-module-imports = true
+

render_engine_json-0.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

render_engine_json-0.0.0/src/render_engine_json/__init__.py

@@ -0,0 +1,2 @@
+from .collection import JSONCollection
+from .parsers import JSONPageParser

render_engine_json-0.0.0/src/render_engine_json/parsers.py

@@ -0,0 +1,64 @@
+import json
+
+from render_engine.parsers.base_parsers import BasePageParser
+
+
+def base_parse(body: dict[str, any]) -> tuple[dict[str, any], str]:
+    """
+    parse content and attributes from content
+    >>> base_parse({"title": "Hello", "content": "Hello World"})
+    >>> ({'title': 'Hello'}, 'Hello World')
+    """
+    content = body.pop("content", None)
+    return body, content
+
+
+def parse_from_slug_entry(
+    slug_entry: dict[str, dict[str, any]]
+) -> tuple[dict[str, any], str]:
+    """
+    Fething content and attributes from a slug entry.
+    >>> parse_from_slug_entry({"slug": {"content": "Hello World"}})
+    >>> ({'slug': 'slug'}, 'Hello World')
+
+    This function expects input to be a dictionary with a single key whose value is a dict.
+    """
+
+    attrs, content = base_parse(list(slug_entry.values())[0])
+    attrs["slug"] = list(slug_entry.keys())[0]
+    return attrs, content
+
+
+class JSONPageParser(BasePageParser):
+    """Parser for JSON content."""
+
+    @staticmethod
+    def parse_content_path(content_path: str) -> dict[str, Any]:
+        """
+        Fetches content from a content_path and set attributes.
+        """
+        with open(content_path, "rb") as json_file:
+            return json.load(json_file)
+
+    @staticmethod
+    def parse_content(content: str) -> tuple[dict[str, Any], str]:
+        """
+        Fetching content and atttributes from content.
+
+        If the parsed_content is a dictionary, then the attributes are fetched from the dictionary
+          and the content is fetched from the "content" key.
+        If the parsed_content is a list, each item is passed as a dictionary into the `data` attribute.
+        """
+
+        body = json.loads(content)
+
+        if isinstance(body, dict):
+            return parse_from_slug_entry(body)
+
+        if isinstance(body, list):
+            return {"data": body}, ""
+
+        raise TypeError(
+            "The content should be a stringified dictionary or list.\n \
+            Perhaps you meant to stringify the content?"
+        )

render_engine_json-0.0.0/src/render_engine_json.egg-info/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.1
+Name: render-engine-json
+Version: 0.0.0
+Summary: JSON Parser and Collection for Render Engine
+Project-URL: homepage, https://github.com/kjaymiller/render_engine_json/
+Project-URL: repository, https://github.com/kjaymiller/render_engine_json/
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: render-engine>=2023.12.1b3
+Requires-Dist: python-slugify
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+
+# Render Engine JSON
+
+JSON Parser and Collection Module for Render Engine
+
+## Installation
+
+```bash
+pip install render_engine_json
+```
+
+## Usage
+
+The `render-engine-json` extends render-engine to allow you to build pages and collections using JSON. 
+
+The `JSONPageParser` class can be used to parse a single JSON page and the `JSONCollection` class can be used to parse a single collection of JSON pages.
+
+> **NOTE**
+> The `JSONCollection` class is designed to work with a single JSON file that contains an array of JSON Objects or a JSON Hash where the keys are the slugs. If you want to work with multiple JSON files you can use a regular `Collection` and the `JSONPageParser` as the parser.
+
+### Single JSON Page Entry
+
+To create a json entry you will need the `JSONPageParser` class as the Parser for your `Page` Object.
+
+You can pass the page a json string or a json file path.
+
+#### As a string
+
+```python
+
+from render_engine import Page, Site
+from render_engine_json import JSONPageParser
+
+site = Site()
+
+json_page = """
+{
+    "title": "My JSON Page",
+    "content": "This is my json page"
+}
+"""
+
+@site.page
+class JSONStringPage(Page):
+    parser = JSONPageParser
+    content = json_page
+
+```
+
+#### As a file
+
+```python
+
+@site.page
+class JSONFilePage(Page):
+    parser = JSONPageParser
+    content_path = "path/to/json/file.json"
+
+```
+
+### JSON Collection
+
+To create a JSON collection you will need the `JSONCollection` Object.
+
+You can pass the collection a json string or a json file path.
+
+#### As a string
+
+```python
+from render_engine import Site, Collection
+from render_engine_json import JSONCollection, JSONPageParser
+
+site = Site()
+
+json_collection = """
+[
+    {
+        "title": "My JSON Page",
+        "content": "This is my json page"
+    },
+    {
+        "title": "My JSON Page 2",
+        "content": "This is my json page 2"
+    }
+]
+"""
+
+@site.collection
+class JSONStringCollection(Collection):
+    parser = JSONPageParser
+    content = json_collection
+
+```
+
+
+```

render_engine_json-0.0.0/src/render_engine_json.egg-info/SOURCES.txt

@@ -0,0 +1,17 @@
+.gitignore
+.pre-commit-config.yaml
+README.md
+pyproject.toml
+test_JSONPage_parser.py
+.devcontainer/devcontainer.json
+.github/CODE_OF_CONDUCT.md
+.github/LICENSE.md
+.github/workflows/publish.yml
+.vscode/settings.json
+src/render_engine_json/__init__.py
+src/render_engine_json/parsers.py
+src/render_engine_json.egg-info/PKG-INFO
+src/render_engine_json.egg-info/SOURCES.txt
+src/render_engine_json.egg-info/dependency_links.txt
+src/render_engine_json.egg-info/requires.txt
+src/render_engine_json.egg-info/top_level.txt

render_engine_json-0.0.0/src/render_engine_json.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

render_engine_json-0.0.0/src/render_engine_json.egg-info/requires.txt

@@ -0,0 +1,5 @@
+render-engine>=2023.12.1b3
+python-slugify
+
+[dev]
+pytest

render_engine_json-0.0.0/src/render_engine_json.egg-info/top_level.txt

@@ -0,0 +1 @@
+render_engine_json

render_engine_json-0.0.0/test_JSONPage_parser.py

@@ -0,0 +1,19 @@
+import pytest
+
+from render_engine_json.parsers import JSONPageParser
+
+
+def test_JSONPageParser_parses_content_no_slug():
+    CONTENT = '{ "title": "Hello", "content": "Hello World" }'
+    assert JSONPageParser().parse_content(CONTENT) == (
+        {"title": "Hello"},
+        "Hello World",
+    )
+
+
+def test_JSONPageParser_parses_content_with_slug():
+    CONTENT = '{ "slug": { "title": "Hello", "content": "Hello World" } }'
+    assert JSONPageParser().parse_content(CONTENT) == (
+        {"slug": "slug", "title": "Hello"},
+        "Hello World",
+    )