-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap ( Next Update ) #19
Comments
What do you think of also including [FEATURE] Create zettel child/singling without opening new note #22 ? |
Also I am gona try to work on making sure everything has a config option though that may mean it should have an advanced section of the config not just throw everything at people so they don't feel overwhelmed at start. |
If anyone is looking for it the issue with the links is being fixed in the next update. |
My preference would be to focus on bugs for 1.1.1 and start adding new features in the next release. |
@Dyldog Any chance we could get milestones enabled? 🙂 |
Fair point! In that case get on thos PRs I put in so we can get this thing out the door! :p I think after those PRs we may have all the bugs smashed. |
I've took the freedom to create some milestones and add some issues there. Please, take a look and share your thoughts. |
Awesome initiative! Thank you! I really need to learn milestones! |
Thanks for all your help, guys. Things got really busy for me over the last week or so. I'll be back to helping out as soon as I can. |
The main thing is we got those bug fixes out the door so thats good. People can use it. |
Could you please add the option to not add the zettel's title as an H1 in the newly created file? It may not be needed for people like me who name zettels with Note that this might interfere with the Insert Zettel Link function, which seems to look for H1s. |
Please create an issue for this. Also before creating an issue please look at some of the other feature requests for example #13 I believe will solve your use case. If it does please just add a note in that issue about your use case. If not address in your feature request issue why #14 does not solve your use case. |
No worries man everyone gets busy. Sorry if I got a little impatient and pushed the version out the door lolz |
No complaints here. 🙂 The whole point of having multiple maintainers is that all of them can keep moving the project forward, right? |
Looking for input, as far as a roadmap is concerned. My thought is to release a version
1.1.1
as a general bug fix release, which is well on its way. Passed that, I'm open to suggestions.Planned
1.1.1
- Bug FixesFuture
The text was updated successfully, but these errors were encountered: