-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add hex colors detection #59
Conversation
… into palette # Conflicts: # src/haxeLanguageServer/documents/HxTextDocument.hx
Yes (also called from npm postinstall), this is all i get now:
There is |
|
it seems like you are running everything from vshaxe project. |
Thanks, with opened subproject things are working. |
There is |
No, we don't want to add a redundant setting if it can be done with a built-in one. |
both (global and Haxe specific) setting work fine according to my quick tests. |
Why not? They should be kept in sync, otherwise you can't build vshaxe with a current server version... |
@RblSb I noticed that we turn lowercase hex into uppercase hex in the color editor. We should try to preserve casing if possible. |
Do you want to keep casing for every character or only low/high new string case based on first character after |
Good question, not sure about mixed casing... I don't think you even can fully preserve casing there, after all, a position that was previously a number might turn into a letter after changing the color in the editor, and then you have nothing to base the decision on. So it's probably best to base it on the first letter. |
0x00112233 is detected as uppercase
Works out of box it seems. Please bind with vscode option by yourself, i have no idea about correct server handling. Some description suggestion:
(also null access fix for
updateActiveEditorPackage
)