ignore private methods and non-settable properties

[felixdesouza]

Before this PR

If you had an abstract class with private methods or public methods with parameters, it would try to start assigning those fields even though it doesn't make any sense.

After this PR

==COMMIT_MSG==
Stricter filtering on what is and isn't settable.
==COMMIT_MSG==

Now we ensure that for a method to be assigned it:

• is not private
• is a zero arg method
• it's either nested
• or it is settable i.e. derives from some sort of Property, had to include ConfigurableFilesCollection as I had missed that last time round.

Possible downsides?

It feels very whack-a-mole. It gets us to our goal of more parallelisable things, but I wonder whether we can do a two-pronged approach with trying to attack the configuration cache (which supposedly gets you parallel runs for free as well).

[changelog-app]

Generate changelog in changelog/@unreleased

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Stricter filtering on what is and isn't settable.

Check the box to generate changelog(s)

• Generate changelog entry

[svc-autorelease]

Released 1.4.0