-
**Describe the bug**
When the metadata returned has all fields stored in UPPERCASE LETTERS, `--autoname` cannot process it properly
**Branch**
dev
**To Reproduce**
Steps to reproduce the beha…
ckf42 updated
8 months ago
-
This is very much nice-to-have, but it would make sense for all the code generated by migra to be consistent in its formatting. Right now some statements are lowercase (e.g. `drop function`) and some …
-
```
Adding an "uppercase letter boundary" to semantic cleanup score will make code
diffs look nicer.
For example,
cleanupSemanticScore
would be changed to
cleanupSemanticScore
This might be useful …
-
```
https://twitter.com/Piercy0812/status/324882111624527873
```
Original issue reported on code.google.com by `dcrossland@google.com` on 27 Apr 2013 at 11:38
-
```
Adding an "uppercase letter boundary" to semantic cleanup score will make code
diffs look nicer.
For example,
cleanupSemanticScore
would be changed to
cleanupSemanticScore
This might be useful …
-
```
Reproducing the problem:
1. Try to enable telnet with lower-case or mixed-case MAC address
2. Telneting in won't work
Fix: Enable telnet with the MAC address's characters (A-F) in upper-case.
W…
-
```
Adding an "uppercase letter boundary" to semantic cleanup score will make code
diffs look nicer.
For example,
cleanupSemanticScore
would be changed to
cleanupSemanticScore
This might be useful …
-
```
Adding an "uppercase letter boundary" to semantic cleanup score will make code
diffs look nicer.
For example,
cleanupSemanticScore
would be changed to
cleanupSemanticScore
This might be useful …
-
```
What steps will reproduce the problem?
1. Set rotation mode to "automatic".
2. Open local session.
3. Tilt display to landscape.
4. Open virtual keyboard.
What is the expected output? What do you…
-
```
Adding an "uppercase letter boundary" to semantic cleanup score will make code
diffs look nicer.
For example,
cleanupSemanticScore
would be changed to
cleanupSemanticScore
This might be useful …