c9f19d8663
I have run the VSCode Extension [markdownlint](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint) on all Markdown Files in the Repo. The provided Rules are documented here: https://github.com/DavidAnson/markdownlint/blob/v0.23.1/doc/Rules.md Rules I didn't follow/fix: * MD024/no-duplicate-heading * Changelog: Here Heading will always repeat. * Examples Readme: Platform-specific documentation should be symmetrical. * MD025/single-title * MD026/no-trailing-punctuation * Caused by the ! in "Hello, World!". * MD033/no-inline-html * The plugins_guidlines file does need HTML, so the shown badges aren't downscaled too much. * ~~MD036/no-emphasis-as-heading:~~ * ~~This Warning only Appears in the Github Issue Templates and can be ignored.~~ * ~~MD041/first-line-heading~~ * ~~Only appears in the Readme for the AlienCake example Assets, which is unimportant.~~ --- I also sorted the Examples in the Readme and Cargo.toml in this order/Priority: * Topic/Folder * Introductionary Examples * Alphabetical Order The explanation for each case, where it isn't Alphabetical : * Diagnostics * log_diagnostics: The usage of inbuild Diagnostics is more important than creating your own. * ECS (Entity Component System) * ecs_guide: The guide should be read, before diving into other Features. * Reflection * reflection: Basic Explanation should be read, before more advanced Topics. * WASM Examples * hello_wasm: It's "Hello, World!".
25 lines
547 B
Markdown
25 lines
547 B
Markdown
---
|
|
name: Feature Request
|
|
about: Propose a new feature!
|
|
title: ''
|
|
labels: ''
|
|
assignees: ''
|
|
---
|
|
|
|
## What problem does this solve or what need does it fill?
|
|
|
|
A description of why this particular feature should be added.
|
|
|
|
## What solution would you like?
|
|
|
|
The solution you propose for the problem presented.
|
|
|
|
## What alternative(s) have you considered?
|
|
|
|
Other solutions to solve and/or work around the problem presented.
|
|
|
|
## Additional context
|
|
|
|
Any other information you would like to add such as related previous work,
|
|
screenshots, benchmarks, etc.
|