We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Often command module descriptions contain HTML (which kinda sucks).
This is occasionally used for formatting, which is fine.
There are many instances where the description only uses HTML to include links.
It would make much more sense to define a references: key in the module config YAML file to contain an array of reference URLs.
references:
The admin UI should also be updated to display the reference URLs.
The text was updated successfully, but these errors were encountered:
We would then advise that no HTML used in description, correct? Is there any other reason to have html in description?
Sorry, something went wrong.
Unfortunately we don't have much choice. Formatting inside the description is useful and HTML is the easiest approach.
Links are long and there's no need to have them inside the description.
No branches or pull requests
Often command module descriptions contain HTML (which kinda sucks).
This is occasionally used for formatting, which is fine.
There are many instances where the description only uses HTML to include links.
It would make much more sense to define a
references:
key in the module config YAML file to contain an array of reference URLs.The admin UI should also be updated to display the reference URLs.
The text was updated successfully, but these errors were encountered: