allow non-Symbol object properties on RSAA

[darthrellimnad]

Here's the proposed change regarding Issue #188.

Dev setup was easier than expected and worked just as described! 👍Let me know if I need to change anything for convention, or add/edit additional tests or documentation.

This change only removes this requirement from the validateRSAA method, and from the documentation. It doesn't seem as if anything else in the codebase requires the old behavior.

This is still a breaking change though and does effect the existing RSAA specification, so probably best grouped into a future major (v3+) release after ppl have time to discuss in this PR (and if we still want to make this change) :)

[nason]

Thanks @darthrellimnad! This looks good to me.

Like I said in the issue, I don't know why this was part of the RSAA spec. At the same time, I don't see the harm in changing it.

Let's leave this open for a few days so people can chime in. If no issues are raised I'm happy to merge this in as-is 👍

[nason]

@darthrellimnad I just cut a new next branch for a 3.0 release. Can you update this PR to target that branch instead?

[coveralls]

Coverage remained the same at 100.0% when pulling d374151 on darthrellimnad:major/issue-188-custom-rsaa-props into 3a19b1b on agraboso:next.

[darthrellimnad]

@nason I rebased with next and fixed a merge conflict with the test file. Looked like 2 changes each used the action29 case, so I changed my added Symbol prop test to action30. Let me know if you need anything else 👍

[nason]

Awesome, thanks! I'm going to go ahead and merge this into next so I can publish a beta later today.

[nason]

This has been released in 3.0.0-beta.0