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

[unstable option] format_strings #3353

Open
Tracked by #83 ...
scampi opened this issue Feb 13, 2019 · 7 comments
Open
Tracked by #83 ...

[unstable option] format_strings #3353

scampi opened this issue Feb 13, 2019 · 7 comments
Labels
unstable option tracking issue of an unstable option

Comments

@scampi
Copy link
Contributor

scampi commented Feb 13, 2019

Tracking issue for unstable option: format_strings

@scampi scampi added the unstable option tracking issue of an unstable option label Feb 13, 2019
@scampi scampi changed the title [unstable option] unstable option: format_strings [unstable option] format_strings Feb 18, 2019
@ayazhafiz
Copy link
Contributor

ayazhafiz commented Jul 11, 2020

blocked by: #4036

@AurevoirXavier
Copy link

blocked by: #4036

It looks like no more block.

@corneliusroemer
Copy link

Would be great if this could get merged @ayazhafiz

@ytmimi
Copy link
Contributor

ytmimi commented May 23, 2022

@corneliusroemer unfortunately there are still some outstanding issues that are going to block stabilization. For example #4323, #5138, #5003. There are likely others, but I was able to quickly find those in the issue tracker

@yodaldevoid
Copy link
Contributor

Both #4323 and #5138 may have been resolved by #5201, though this obviously needs testing.

@ytmimi
Copy link
Contributor

ytmimi commented May 23, 2022

@yodaldevoid thanks for pointing that out. If you've got the bandwidth or interest to test the associated code snippets on the latest master that would be great, otherwise I can look into this a little later!

@calebcartwright
Copy link
Member

We have a well documented process for stabilizing options and all options are presumed to need to remain unstable unless and until they can easily clear those thresholds, regardless of whether an option is 5 days old or 5 years old.

This option is still unstable because that hasn't happened yet. Additionally, there are a number of outstanding questions associated with this option, particularly as it relates to desired break points as well as whether this option could/should be used to unwrap/collapse broken strings.

One challenge we currently have, and where the community could help (especially if you'd like to see an option stabilized), is that there are a number of open, config option related bugs on the backlog that haven't been linked to the corresponding tracking issue. Even something as small as that (which anyone with a GitHub account could do) would be a small but useful step towards stabilization, and as discussed in the last couple comments, fixing or even just reconfirming associated bugs would be helpful too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
unstable option tracking issue of an unstable option
Projects
None yet
Development

No branches or pull requests

7 participants