dromse / obsidian-gamified-tasks

Gamify your task management with rewards system, craft your tasks by tags.
MIT License
40 stars 2 forks source link

[Bug]: Reading Properties as items in Rewards/History pool #43

Closed Ackasi closed 4 months ago

Ackasi commented 4 months ago

What happened?

My properties, which regenerate due to syncing complications and such, are read by the Grind Manager reward menu as individual items for rewards, and I am unable to remove them

Steps to reproduce

create the rewards/history doc, have file properties, shows in menu.

Plugin Version

Recent

Obsidian Version

Recent

What platform are you seeing the problem on? (Can be multiple)

Windows

Relevant log output

N/A

Additional questions

dromse commented 4 months ago

Hi, @Ackasi, for history file you can change format to .txt or other which removes file from obsidian indexing I think it can help somehow. Later I will add feature for ignore frontmatter in rewards file.

Thanks for a bug report!

dromse commented 4 months ago

@Ackasi, does changing the history file format help? I'm about to start working on this bug report. To clarify, will it be sufficient to add a feature that ignores the frontmatter in the rewards file?

Ackasi commented 4 months ago

it didn't seem to make much of a difference, i think the feature would be necessary

On Sun, May 26, 2024 at 9:15 AM dromse @.***> wrote:

@Ackasi https://github.com/Ackasi, does changing the history file format help? I'm about to start working on this bug report. To clarify, will it be sufficient to add a feature that ignores the frontmatter in the rewards file?

— Reply to this email directly, view it on GitHub https://github.com/dromse/obsidian-grind-manager/issues/43#issuecomment-2132274731, or unsubscribe https://github.com/notifications/unsubscribe-auth/AY5NIEI53TCYA5O7KNV5AYTZEIDB7AVCNFSM6AAAAABIIFUFRGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGI3TINZTGE . You are receiving this because you were mentioned.Message ID: @.***>

dromse commented 4 months ago

@Ackasi, update to new version, I fixed it in 1.2.3.