mikeckennedy / markdown-subtemplate Goto Github PK

The methods on the storage engine return str. They should return Optional[str] because we cannot be sure they exist in a given deployment.

Here's what I have in mind. We have a landing page and want to specify which campaign this is about all the while reusing most of the content:

# The landing page title

Welcome people from this campaign

[VARIABLE name=value]

[IMPORT section1] # {name: value} is added to the variables passed here.
[IMPORT section2]
[IMPORT section3]

Introduced in #7 but not yet documented.

Hi,
would you be so kind and add some sort of hello-world or "for-dummies" sample script in the README demonstrating how to use this package, please?

I want to use this with FastAPI and Beanie

What's your opinion on the best way forward?

Should I work on rewriting the functions in my fork of markdown-subtemplate or would the solution be as simple as using unsync to fix it. I'll re-watch a few of the videos in your async python course and see if I can pull it off either way. If I get something working I'll submit a pull request.

Two quick examples make sense:

• SQLAlchemy
• MongoDB (via MongoEngine)