Skip to content
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

Open
brannonh opened this issue Sep 7, 2022 · 14 comments
Open

Roadmap ( Next Update ) #19

brannonh opened this issue Sep 7, 2022 · 14 comments
Labels
help wanted Extra attention is needed

Comments

@brannonh
Copy link
Collaborator

brannonh commented Sep 7, 2022

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 Fixes

Future

@brannonh brannonh added the help wanted Extra attention is needed label Sep 7, 2022
@Eforen
Copy link
Collaborator

Eforen commented Sep 9, 2022

What do you think of also including

[FEATURE] Create zettel child/singling without opening new note #22 ?

@Eforen
Copy link
Collaborator

Eforen commented Sep 9, 2022

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.

@Eforen Eforen changed the title Roadmap Roadmap ( Next Update ) Sep 9, 2022
@Eforen
Copy link
Collaborator

Eforen commented Sep 9, 2022

If anyone is looking for it the issue with the links is being fixed in the next update.

@brannonh
Copy link
Collaborator Author

brannonh commented Sep 9, 2022

What do you think of also including

[FEATURE] Create zettel child/singling without opening new note #22 ?

My preference would be to focus on bugs for 1.1.1 and start adding new features in the next release.

@brannonh
Copy link
Collaborator Author

brannonh commented Sep 9, 2022

@Dyldog Any chance we could get milestones enabled? 🙂

@Eforen
Copy link
Collaborator

Eforen commented Sep 10, 2022

What do you think of also including
[FEATURE] Create zettel child/singling without opening new note #22 ?

My preference would be to focus on bugs for 1.1.1 and start adding new features in the next release.

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.

@jvanz jvanz modified the milestones: 1.2.0, 1.1.1 Sep 10, 2022
@jvanz
Copy link
Collaborator

jvanz commented Sep 10, 2022

I've took the freedom to create some milestones and add some issues there. Please, take a look and share your thoughts.

@Eforen
Copy link
Collaborator

Eforen commented Sep 10, 2022

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!

@brannonh
Copy link
Collaborator Author

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.

@Eforen
Copy link
Collaborator

Eforen commented Sep 16, 2022

The main thing is we got those bug fixes out the door so thats good. People can use it.

@DesiQuintans
Copy link

DesiQuintans commented Sep 20, 2022

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 ID separator title.md, especially when paired with a plugin like Embedded note titles.

Note that this might interfere with the Insert Zettel Link function, which seems to look for H1s.

@Eforen
Copy link
Collaborator

Eforen commented Sep 20, 2022

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 ID separator title.md, especially when paired with a plugin like Embedded note titles.

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.

@Eforen
Copy link
Collaborator

Eforen commented Sep 20, 2022

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.

No worries man everyone gets busy.

Sorry if I got a little impatient and pushed the version out the door lolz

@brannonh
Copy link
Collaborator Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants