-
-
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
OptionList items use GUID as key (plus debug!) #1515
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From our in-person work on this issue, this is totally fine with me and is well documented. It's a small but important change to enable C# debugging in the LFMerge docker environment.
The only thing I might add is an addition comment on why elevated privileges are necessary. As best as I can remember (and it's already fading), privileged: true
is needed in order to attach a debugger to a running process inside the docker container. This is an OS kernel-level feature not available in regular unprivileged containers. That's what I remember, anyway
…alue. This was mostly already being done, but one place in the html (when the field is uneditable) and one in the php (when option list items are constructed without a given key). The LFMerge side is still not working, but there aren't any obvious changes required yet in this repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make sure to resolve that conflict and clean up the PR description a bit before you merge.
Agreed - the PR is now doing more than just adding elevated privs for debugging. This is changing how keys are used in optionlists |
Don't worry, I'm not going to merge this til the LfMerge side is fixed, and it has a good bit more work to do |
3ebca62
to
edc6ab4
Compare
Fixes # (issue)
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of Change
Only keep lines below that describe this change, then delete the rest.
Screenshots
Please provide screenshots / animations for any change that involves the UI. Please provide animations to demonstrate user interaction / behavior changes
Checklist
How to test
Please describe how to test and/or verify your changes. Provide instructions so we can reproduce. Please also provide relevant test data as necessary. These instructions will be used for QA testing below.
qa.languageforge.org testing
Testers: Check the box and put in a date/time to sign-off/attest the feature works as expected on qa.languageforge.org