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

some issues types can no longer be previewed, impossible to add notes before/after mandatory fields #106877

Open
matthiaskrgr opened this issue Jan 14, 2023 · 3 comments
Labels
A-meta Area: Issues & PRs about the rust-lang/rust repository itself

Comments

@matthiaskrgr
Copy link
Member

cc #106831 @estebank

It looks like yaml templates no longer allow for a "preview" to make sure the issue actually looks nice.
Also there is no way to actually insert text before any of the fields (for diagnostics issues for example) such as "this code is from repo xy file foo.rs" or something like. You have to first post the entire ticket to then modify the generated markdown which is an unpleasant sensation in the rear...

@matthiaskrgr matthiaskrgr added the A-meta Area: Issues & PRs about the rust-lang/rust repository itself label Jan 14, 2023
@estebank
Copy link
Contributor

@matthiaskrgr The ones that changed now have a free form field at the end, but we can add more fields as we desire. What do you think the form should look like? Regarding preview, the text area fields that don't have a preview are meant to be "raw" text, the ones meant for formatted text still have the preview (for that section alone).

@matthiaskrgr
Copy link
Member Author

Perhaps we could add an optional (is that possible) field at the very start before the rust code field?

It would be nice if the fields had a clear indicator how their input will be formatted that can be seen before editing the ticket.

I'm not sure what the best solution is but for me it feels like filling out/fixing these new forms "correctly" (so it looks nice) takes at least 3x as long as the previous template, while providing the same information. :/

@estebank
Copy link
Contributor

I'm in favor of adding more fields to the forms, I was just following the previous prompts. If you have a specific schema design, I'll be happy to review :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: Issues & PRs about the rust-lang/rust repository itself
Projects
None yet
Development

No branches or pull requests

2 participants