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

[REQ] Ability to Export FFlag JSON from the FFlag Editor #923

Closed
1 task done
loustact opened this issue Nov 7, 2023 · 6 comments · Fixed by #1158
Closed
1 task done

[REQ] Ability to Export FFlag JSON from the FFlag Editor #923

loustact opened this issue Nov 7, 2023 · 6 comments · Fixed by #1158

Comments

@loustact
Copy link

loustact commented Nov 7, 2023

Acknowledgement of preliminary instructions

  • I have read and acknowledged the preliminary instructions.

What idea do you have?

Simple request, ability to export FFlag JSON from FFlag Editor as the import function only exists.

This feature would be useful if you want to share your FFlag list to someone else, or doing reinstallations (like uninstalling to switch to using package managers like Scoop, which what I did just a while ago) without manually copy-pasting your list. If you want to pass this list to your other computer if you do have one, having an easy way of exporting the JSON would be convenient. It could also help out smooth brains like me who don't know where the JSON file is usually stored at for these kinds of use cases.

I understand if this won't get added as these are pretty much rare cases, especially reinstallation, for everyday users that haven't encountered any problems. There is really no point in reinstalling if no issues arise to begin with, for example. Though, it would be great to have it in moments in which these cases do arise.

@pizzaboxer
Copy link
Contributor

Open the Mods folder. Go to the ClientSettings folder. It'll be there.

@loustact
Copy link
Author

loustact commented Nov 8, 2023

Open the Mods folder. Go to the ClientSettings folder. It'll be there.

Thank you :)

Sorry for causing a bit of a trouble.

@pizzaboxer
Copy link
Contributor

I mean, I agree with you that it should probably be more easily accessible, but I'm just pointing out that's where they're stored.

@loustact
Copy link
Author

loustact commented Nov 8, 2023

Ah, I misunderstood. Sorry about that.

Anyways, I do hope you consider this in the future :)

@bluepilledgreat
Copy link
Member

#1158

@boblox69
Copy link

guy why i cant put the code/script into export JSON

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

Successfully merging a pull request may close this issue.

4 participants