google / google/yapf

Knob to allow alternative formatting of call chains

Open
#348 15 comments 8 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
14k
Forks
904
PR merge metrics
No merged PRs in 30d

Description

In addition to the standard method of getting call chains formatted like this:
```
rawKPIs = KPIsSession.query(
KPI.name, KPI.value, KPI.created
).filter(KPI.entryId == entryID).filter(KPI.subsetId is None).filter(
KPI.created >= fromUnixTimestamp(fromTimestamp)
).filter(KPI.created <= fromUnixTimestamp(toTimestamp)).filter(
func.unix_timestamp(KPI.created) % moduloSelector == 0
).order_by(KPI.name, KPI.created).all()
```

Allow formatting as:
```
rawKPIs = \
KPIsSession.query(
KPI.name, KPI.value, KPI.created
).filter(
KPI.entryId == entryID
).filter(
KPI.subsetId is None
).filter(
KPI.created >= fromTimestamp
).filter(
KPI.created <= toTimestamp
).filter(
KPI.created % moduloSelector == 0
).order_by(
KPI.name, KPI.created
).all()
```

or:
```
rawKPIs = \
KPIsSession.query(KPI.name, KPI.value, KPI.created) \
.filter(KPI.entryId == entryID) \
.filter(KPI.subsetId is None) \
.filter(KPI.created >= fromTimestamp) \
.filter(KPI.created <= toTimestamp) \
.filter(KPI.created % moduloSelector == 0) \
.order_by(KPI.name, KPI.created) \
.all()
```

This makes the code more readable and stack traces clearer. (due to line number)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.