-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[WIP] Add font family to preferences #78
[WIP] Add font family to preferences #78
Conversation
Really nice, I was able to get 'Arial' in my code editor hahaha. Okay great, I had to add one preference option to work with strings (only supported boolean and number until now), check this commit: 9942d3f. Would be great to move the styles to |
Can you also add a description underneath the Preference option? |
6a0eedd
to
4a00f09
Compare
ah yes, I'm not aware that it's only accepted boolean and number. 😄 Updated with 9942d3f, description, and the moving of style to CodeContainer |
4a00f09
to
617fe66
Compare
Haha, a coincidence. I'm currently implementing Prettier Preferences and now need the Preference type refactor too. Let me take a look. |
Looks good! I made one small change to add specify a placeholder ('Source Code Pro') in the input, makes it more clear on what to input. I think that's enough for the user to see what needs to happen, so we can remove the description. I added the last required commit here: bf114d8. And this is how it looks like: Then it'll be ready to merge! Thanks a lot for this PR, this is very valuable. |
Great! Let's ship this 🚀 |
Oh oops, forgot to change the name. Well, 🤷♂️ |
😅 you move really fast! thank you! |
Haha, thanks. I'm thinking of replacing the preferences system for something that takes less boilerplate, now you need to change 4 things before it works. Very confusing and tedious. |
yup, I missed some things when I first opened the PR. Today I just use this for forms shameless plug plain react and lodash 😄 |
Hmm, interesting. If we could convert the preferences to something like that it would be really nice. Best case would be if we only had to define preferences in the store, and then it automatically gets synced with localStorage when updated. |
maybe under one action? SET_PREFERENCE, and just validate the preference schema for that action payload. |
Yap, that's even better. |
Add font family for preference. AFAIK this should be all from the client side, haven't got to test it yet until we have staging server :)
Also, why do we need to
injectGlobal
here @CompuIves ? I think we can move it toCodeContainer
?