-
Notifications
You must be signed in to change notification settings - Fork 45
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
Bug: 'Copy' checkbox not active by default for all fields #1473
Comments
I'm struggling to get my head around how the Copy system works. I've been digging through the code for ages and I still get work out how it chooses which fields to copy, let alone why some fields don't have the copy checkbox ticked by default. I'll come back to this. |
@matkoniecz any possible thoughts on this one if you're free? |
this is a slightly different one because it's copying verification not attributes |
From another issue: "Architectural style needs autofill for all copy boxes like others" (from colouring-cities#165) |
@matkoniecz maybe you could look at this when you have time? |
Connected to #1471? Close duplicate or merge? |
BTW, I see
and
in browser logs on using copy checkboxes. It seems that broken checkboxes start as undefined, while marked by default start as |
I've looked in the code, and I still can't find any difference between (for example) "location_address_source" (which defaults to checked) and "location_subdivisions_source_type" (which doesn't). The code is the same, they're using the same props.copy value... Unless the copy value is defined somewhere else in the code and I missed a step when I was adding these new properties to the code...? But I've been digging around and I can't find anywhere that lists the fields that are allowed to be copied or anything like that. |
On some fields, such as those under "Energy Performance -> Retrofit history", the Copy [/] buttons appear, but are not checked by default, like they are on other fields. I had a quick look into this, but couldn't work out what was causing it.
The text was updated successfully, but these errors were encountered: