| Summary: | Editing repo config setting should prefill initial value in field | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mark Macdonald <mamacdon> | ||||
| Component: | Git | Assignee: | Michael Rennie <Michael_Rennie> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | Michael_Rennie, Szymon.Brandys | ||||
| Version: | 3.0 | Flags: | Szymon.Brandys:
review+
|
||||
| Target Milestone: | 5.0 M1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Mark Macdonald
The problem seems to be the way Git is using the commands and the way the command framework works. In this case, they create the 'edit' command once and render it N times, but once the command is created and the command parameter passed in, there is no way to update it prior to rendering (I could be missing something here). Feels to me like we have a few options 1. create one command / command param instance per entry, which would be more work / more memory use 2. add some sort of callback so that a command / command param can ask for its initial value 3. add the ability to pass in a default value when we want the command rendred Created attachment 236506 [details]
proposed fix
Or, I could just pass in a getParameters function and set the value when we create the command parameter.
Szymon, please have a look at the patch (In reply to Michael Rennie from comment #3) > Szymon, please have a look at the patch To make things a bit easier I created a pull request: https://github.com/eclipse/orion.client/pull/29 (In reply to Michael Rennie from comment #4) > (In reply to Michael Rennie from comment #3) > > Szymon, please have a look at the patch > > To make things a bit easier I created a pull request: > https://github.com/eclipse/orion.client/pull/29 Thanks Mike. Merged to master. |