Can you please restart tests?

I restarted CI Travis MacOs tests.

@mklement0 Could you please review the change too?

My vote is for not making this change, which is certainly a breaking one:

While the docs don't really say what -Force is for - which should definitely be added - de facto it has served to force addition of objects even if they have unrelated / additional lack properties that map onto existing columns, which is a useful option to have if applied intentionally (that's where the docs come in).

Note that the error message you currently get with incompatible missing properties clearly states that -Force can be used to force appending.

@sethvs:

Please make it clearer up front when your changes will be breaking, and ideally create an issue before starting a PR, ideally by identifying the "bucket" that the change falls into.

Also, sometimes there's an alternative to a breaking change: in #6797 you tried to simply rename a parameter, but the better course of action is to add an alias.

I've opened a docs issue to request documentation of the current behavior: MicrosoftDocs/PowerShell-Docs#2392

@mklement0 Agree about -Force.
This is what discussion for.
Closing.

@sethvs:

Glad to hear it.

The reason I was suggesting creating an issue before submitting a PR is that the issue allows a broader discussion as to whether and how to implement a change / feature first.

I know that this PR was simple, but generally you run the risk of wasted effort without having consensus on what should be done first.