foam VS Graphene

Source: (1) A personal knowledge management and sharing system for VSCode - Foam. https://foambubble.github.io/foam/. (2) A personal knowledge management and sharing system for VSCode. https://github.com/foambubble/foam. (3) Loam - Visual Studio Marketplace. https://marketplace.visualstudio.com/items?itemName=ciceroisback.loam.

You should have a look at Foam: https://github.com/foambubble/foam

I started using Foam[0] a few years ago, but the more I used it, the more I dropped all the tedious bits, and it became nothing more than a big, evolving markdown repo.

When I switched from vscode (back) to vim, it has worked as well or better than it did before. I follow my own rules. I like the Zettelkasten idea of one idea per card, but if I put more related things in the same .md file, that's OK. I didn't like the flat directory structure, and so I have dirs organized by category. My /bar directory is inside my /cooking directory, and for whatever reason, that makes sense to me. Ripgrep doesn't care, and I always find what I'm looking for.

This markdown hierarchy, that still lives in a repo called "foam", has become indispensable to me.

[0] https://github.com/foambubble/foam

Probably use foam https://github.com/foambubble/foam

So I switched to FOAM and it's just clean & organized markdown files in a git repo. Self host a code server instance and I can reference it without installing something to the work machine.

Recently I started to configure my digital garden. Foam is a good option, Hugo Doks, No Style Please, Git-Wiki, Researcher, Thinkspace, and other themes are good for zetteltasken pages.

I use foam and VSCode and regularly am wow'd with what I am having it do next. I feel I am still just getting started too.

I've wondered about using obsidian with foam as a web editing fallback.

Since the data store is markdown and can be synced with Git, you can already work with an Obsidian vault using Foam in VSCode. I do.

You do need to align some options in each, such as file naming, a header, a particular style of links, and ensure frontmatter behavior. All necessary settings exist.

https://foambubble.github.io/foam/

https://github.com/foambubble/foam/issues/46

This supports basic static file and links functionality, not extended data tools etc., of course.

And gqlgen is not alone in this. We found several more GraphQL frameworks that don’t take it upon themselves to address this problem. Widely used GraphQL server implementations, such as graphql-go/graphql and Python’s graphene, have the exact same gap of exposing messages of unexpected errors by default.

There are multiple Python-based GraphQL libraries and they all vary slightly from each other. For the longest time, Graphene was a natural choice as it was the oldest and was used in production at different companies, but now other newer libraries have also started gaining some traction.

> But you need to know that Wasmer and its sibling projects will stay free forever. We are open source lovers, all of us, and we have a strong background on working on open source projects before joining Wasmer too.

That's great. I'm sure the closed source paid 10x faster editions of the graphene Python GraphQL server written by Syrus "CEO of Graphene" and CEO of wasmer will be open sourced in this spirit.

https://github.com/graphql-python/graphene/issues/268#issuec...

http://graphql-quiver.com/

CloudinaryField is a custom model field not a django built in one and graphene-python doesn't know what do with it. See the list of types it does https://github.com/graphql-python/graphene/tree/master/graphene/types

Thanks for the reply, I was looking at Strawberry a bit but not enough documentation for a graphql noob like me... Hate to turn this into tech support but could you potentially answer a question for me? I'm having a really hard time figuring out how to do this. Given this example: https://github.com/graphql-python/graphene/blob/master/examples/simple_example.py and a slight modification:

Graphene was one of the first (if not the first) lib built on top of graphql-core to provide an easy to use api to build graphql applications. It's been around since 2015 and has a lot of integrations built for it (e.g. Django, SQL Alchemy, etc).