Summary

Fix BaseRepositorySubForm to use new name for adding field prefixes.

Review Request #11719 — Created July 15, 2021 and submitted July 19, 2021, 11:05 p.m.

Information

Owner

david

Repository

Review Board

Branch

release-4.0.x

Bugs

Depends On

Reviewers

Groups

reviewboard

People

Description

In 1.11, Django renamed Form.addprefix to Form.add_prefix. When we
updated to it, we never made the change, and so the repository forms
were still calling the old function. This didn't affect any of the
built-in SCMTools, but for third-party tools that want to prefix keys
into the extra_data, it was failing.

Testing Done

Used in conjunction with an external SCMTool.

Commits

Summary	ID
Fix BaseRepositorySubForm to use new name for adding field prefixes. In 1.11, Django renamed `Form.addprefix` to `Form.add_prefix`. When we updated to it, we never made the change, and so the repository forms were still calling the old function. This didn't affect any of the built-in SCMTools, but for third-party tools that want to prefix keys into the extra_data, it was failing. Testing Done: Used in conjunction with an external SCMTool.	59477e0d2423c95b16ec00b12ded2f36c17ba3d9

Summary

Fix BaseRepositorySubForm to use new name for adding field prefixes.

In 1.11, Django renamed `Form.addprefix` to `Form.add_prefix`. When we updated to it, we never made the change, and so the repository forms were still calling the old function. This didn't affect any of the built-in SCMTools, but for third-party tools that want to prefix keys into the extra_data, it was failing. Testing Done: Used in conjunction with an external SCMTool.

59477e0d2423c95b16ec00b12ded2f36c17ba3d9

flake8 passed.

JSHint passed.

Ship it!

```
Ship It!
```

Status:: Completed
Change Summary:: Pushed to release-4.0.x (8f9db5c)