~ultimaker/uranium/+git/Uranium:4.7

Last commit made on 2020-08-27
Get this branch:
git clone -b 4.7 https://git.launchpad.net/~ultimaker/uranium/+git/Uranium

Branch merges

Branch information

Name:
4.7
Repository:
lp:~ultimaker/uranium/+git/Uranium

Recent commits

3ed9c4d... by Jelle Spijker <email address hidden>

Merge pull request #633 from Ultimaker/fix_fast_config_parser

Fix key value pairs in comments being parsed as seperate values

0100538... by Jelle Spijker <email address hidden>

Added newline at end of file

CURA-7671 Start/end g-code with equal signs gets lost

8eb003b... by Ruben D

Expand fuzz test with more weird symbols

Contributes to issue CURA-7671.

453429f... by Ruben D

Add fuzz test for the FastConfigParser to behave the same as ConfigParser

Hopefully this makes the result more stable.
Had to limit the randomness of the fuzz test a lot though, to ensure that the normal ConfigParser didn't error out on it.

Contributes to issue CURA-7671.

9161bed... by Ruben D

Also test indentation with tabs

ConfigParser seems to generate that. Maybe only in newer Python versions or something, but it does.

Contributes to issue CURA-7671.

20b8edc... by Ruben D

Allow tabs as indentation and as separator too

The ConfigParser serialises multi-line values with tabs to indent them. This is how it knows when the value ends. We should parse it similarly.

Contributes to issue CURA-7671.

7b4527d... by Jaime van Kessel <email address hidden>

Use spaces instead of tab

Co-authored-by: Ghostkeeper <email address hidden>

bac629a... by Jaime van Kessel <email address hidden>

Fix incorrect test data

It used to (incorrectly) accept a line that started with a space
as a key. It shouldn't do this.

f84e753... by Jaime van Kessel <email address hidden>

Fix key value pairs in comments being parsed as seperate values

Fixes Ultimaker/Cura#8235
Fixes Ultimaker/Cura#8230

793e0f5... by Ruben D

Merge branch '4.7' of https://github.com/Patola/Uranium into Patola-4.7