waynevanson / data-entry-obsidian-plugin Goto Github PK

View Code? Open in Web Editor NEW

22.0 22.0 0.0 4.9 MB

Create forms that modify data in existing notes; the dataview plugin for data entry.

License: MIT License

JavaScript 7.15% TypeScript 64.98% Shell 1.02% Rust 26.85%

data-entry obsidian obsidian-plugin

data-entry-obsidian-plugin's Introduction

Why did the mathematician purchase so much moisturiser? Because he loves applying the product (x)

data-entry-obsidian-plugin's People

Contributors

Stargazers

Watchers

data-entry-obsidian-plugin's Issues

Replace changesets with semantic-release

changesets sucks, semantic release is way better with more customisability.

Add license

Something that says "this is mine. you can use it and you can copy code but if you release anything related with it you must give me credit"

Add code fence to data source

Currently the source of our json data is in a markdown file, which is not nice to read.

Instead, we can put it in a codefence so it looks nice.

Requires us to read the file and then extract the code that is only in the code fence.

Add custom extension-name code fence register

Code blocks should look like

```yaml data-entry
# ..schema
```

Instead of

```yaml-data-entry
# ..schema
```

Requires us to create our own codeblock registering function.

Index should be set when one item exists

Add changesets to CI

Use Changesets to create releases, so I can continue trunk based development.

Avoid iterating all file to find a file by path

https://github.com/obsidianmd/obsidian-releases/blob/master/plugin-review.md#avoid-iterating-all-files-to-find-a-file-by-its-path

Hello! Very nice plugin you are developing.
I have been looking for easier ways to create new notes that are fool proof, easy to trigger and that are ideally mobile friendly. Your solution looks like one that can fit that all.
However, I think I'm missing a feature (or two 😅) to match my objectives. This can be achieved in variety of ways, so which one or which ones to pick may be nice to debate if you are willing to do it.

My current workflow uses templater or quickAdd. When I create a new note from a template I just get a succession of single value prompts that I have to fill one after another. There is no way to have a broader context, and in some cases (because a quickAdd limitation) you don't even have a label.

If your plugin had an API that presents the form in a modal and then returns the values, that will be perfect for my use. I can just call the form that I want (or even several) get the values back and then render the template based on those answers. It feels like a perfect workflow.

I'm not sure how it works currently, but it looks like I need to have a dedicated note for data input, but I'm not sure if it is capable of creating new notes.

An additional nice functionality you could add is having select/multi-select fields that are populated with dataview-js queries. Several plugins like metadata-menu or meta-bind allow this, and I think it will be a very interesting and flexible feature to have.

Thanks!