-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
x/gov: Allow description to have newlines #1776
Comments
Can we just parse all escape codes a la |
Alternatively, we could standardize on a simple text format for descriptions, e.g. Markdown. |
I'd be cool with using markdown. If we do that though, then I think the CLI for governance proposals should allow for reading from files, and we should perhaps get the title from the first line or first occurence of We should parse escape codes in the literal descriptions in the CLI (as you described), regardless of markdown support |
Mhmm, why not have the proposal accept a possible file that adheres to a structure? (e.g. JSON w/ title description, etc...). Parsing first |
Sounds good to me. Would you like to make a seperate proposal issue for reading from files? |
Sure thing! Edit: ref #1852 |
Closes cosmos#1852. Closes cosmos#1776.
Summary
We should parse
\n
in descriptions to allow printing newlines. I think this would make the output format better in the CLI.Proposal
Add a pre-processing step when proposing txs to parse
\n
's in the description as newline characters.For Admin Use
The text was updated successfully, but these errors were encountered: