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

docs(roadmap): update roadmap #11110

Merged
merged 1 commit into from
Oct 26, 2021
Merged

docs(roadmap): update roadmap #11110

merged 1 commit into from
Oct 26, 2021

Conversation

IlCallo
Copy link
Member

@IlCallo IlCallo commented Oct 26, 2021

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Documentation
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • It's submitted to the dev branch (or v[X] branch)
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
  • It's been tested on a Cordova (iOS, Android) app
  • It's been tested on a Electron app
  • Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

@rstoenescu rstoenescu merged commit 60e3d77 into dev Oct 26, 2021
* 🚧 (WIP) Premium video tutorials (pre-access will be a paid service, will be later released for free) ([reference](https://quasarcomponents.com/))
* 🚧 (WIP) Quasar website revamp 🔥
* 🚧 (WIP) Support Cypress Component Testing into Quasar Cypress AE ([reference](https://github.com/quasarframework/quasar-testing/issues/163) [reference](https://github.com/quasarframework/quasar-testing/pull/185))
* Enhance Quasar types to be more precise, provide guidelines for community contributions ([reference](https://github.com/quasarframework/quasar/issues/8642) [reference](https://github.com/quasarframework/quasar/issues/8493) [reference](https://github.com/quasarframework/quasar/issues/11090) [reference](https://github.com/quasarframework/quasar/issues/11043))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried the rendered version and saw that multiple references in a row look kind of confusing. Using the issue handles(e.g. #8642) as the label might look better.

Suggested change
* Enhance Quasar types to be more precise, provide guidelines for community contributions ([reference](https://github.com/quasarframework/quasar/issues/8642) [reference](https://github.com/quasarframework/quasar/issues/8493) [reference](https://github.com/quasarframework/quasar/issues/11090) [reference](https://github.com/quasarframework/quasar/issues/11043))
* Enhance Quasar types to be more precise, provide guidelines for community contributions (references: [#8642](https://github.com/quasarframework/quasar/issues/8642), [#8493](https://github.com/quasarframework/quasar/issues/8493), [#11090](https://github.com/quasarframework/quasar/issues/11090), [#11043](https://github.com/quasarframework/quasar/issues/11043))

Also, we can do the same for others even if there is a single reference, if applicable(_issues, PRs, and discussions). If it's on another repo like quasarframework/rfcs, then we can do quasarframework/rfcs#10. AFAIK, GitHub already handles these types of links in issue comments, descriptions, etc. but on Markdown files. So, we can try to replicate the behavior.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you open a new pr with these changes?

@IlCallo IlCallo deleted the IlCallo-patch-1 branch October 27, 2021 07:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants