feat: Filename Options (projectId) #1178
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
November 19, 2025 23:27
+Added projectId abbreviations style. ie: PROJ-1234. +Added UUIDv4 variable to custom options. +Added short year variable to custom options.
bendavis987
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
I made some custom changes for my workflow and figured I could share if you're interested. The point of this PR is really to gauge your interest, and I can polish them up if so. I also wasn't sure if you had already finished: #791 or #59, so I did those as well while I was in these files.
Filenames move to General Tab
I didn't know the file name configuration was an option initially. This was part of why I started making changes. I can revert this if you prefer it in appearance, but it just didn't seem like it fit there. It should be in the same place as custom folder structure in my opinion.
Filename context vs taskData structure
I apologize if this is bad practice. I don't know much about TS and it's conventions, but this seemed like it made more sense to me. Maybe filenamecontext should extend it. I'm not sure. Probably worth a conversation.
Actually what I wanted done (New Filename Option: projectId)
I really wanted to format the task names similar to JIRA ie: TASK-1234, and if it is related to a project, then it'll get the id from the project. PROJ-1234. This is a bit difficult since there currently isn't a tracker for the file numbering incrementing. I decided to just piggyback off of the duplicate name check for now. For a full feature, this should probably get a menu option to configure starting number, and it can be stored there / in the obsidian workspace somehow.
Related:
Other notes
I had a few questions while debugging. Like I broke the translations somehow, I need to figure that out. And the projects don't seem to just be the project name. I can't cut the strings consistently at the same place.