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

Moved back settingRegistry dependant commands #7332

Closed
wants to merge 1 commit into from

Conversation

ajbozarth
Copy link
Contributor

References

Bug raised in #7295

PR that introduced the bug #6904

Code changes

Due to a still unclear issue, when passing settingRegistry to functions it changes the behavior of the commands that use it.

This change moves the six commands that interact with settingRegistry back to index.ts from commands.ts, where they were moved to in #6904

User-facing changes

The setting for Line Numbers, Word Wrap, and Match Brackets are no longer reset to their default found in CodeEditor.defaultConfig when a change to editorConfig in the settingRegistry is made (eg. changing tab or font sizes).

Backwards-incompatible changes

None

Due to a still unclear issue, when passing settingRegistry to
functions it changes the beahvior of the commands that use it.

This change moves the six commands that interact with settingRegistry
back to index.ts from commands.ts where they were oved in jupyterlab#6904

This fixes jupyterlab#7295
@jupyterlab-dev-mode
Copy link

Thanks for making a pull request to JupyterLab!

To try out this branch on binder, follow this link: Binder

@ajbozarth
Copy link
Contributor Author

@jasongrout I found a bug in my code from last month, this fix needs to go out with 1.2 and 2.0 to prevent introducing the bug into a release. Given this I prioritized fixing the bug over figuring out why it happens. Also after my PR was merged I discovered that there is most like no cases where the addCommand functions I introduced would be used by outside code, so this change would not hurt the original intent of my PR

@jasongrout
Copy link
Contributor

jasongrout commented Oct 12, 2019

This PR doesn't fix the issue for me. I explored the problem a bit in #7295 (comment)

ajbozarth added a commit to ajbozarth/jupyterlab that referenced this pull request Oct 13, 2019
After further testing od my previous pr jupyterlab#7332 I discovered that
the core issue was that config was a var not a const. So the
commands were using the value of config at creation in thier updates
rather than it's value at runtime.
@ajbozarth
Copy link
Contributor Author

Closing in favor of #7350

@ajbozarth ajbozarth closed this Oct 13, 2019
@ajbozarth ajbozarth deleted the bugfix branch October 13, 2019 05:56
@ajbozarth ajbozarth restored the bugfix branch October 14, 2019 23:30
@lock lock bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Nov 14, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Nov 14, 2019
@ajbozarth ajbozarth deleted the bugfix branch December 11, 2019 19:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants