cti-python-stix2/stix2/test
Michael Chisholm 8bbf5fa461 Make extension instances work the same as other objects, with
respect to properties.  Before, properties were declared on
toplevel-property-extension extensions as if they were going
to be used in the normal way (as actual properties on instances
of the extension), but they were not used that way, and there
was some ugly hackage to make it work.  Despite the fact that
property instances were given during extension registration,
they were not used to typecheck, set defaults, etc on toplevel
property extension properties.

I changed how registration and object initialization works with
respect to properties associated with extensions.  Now,
extensions work the same as any other object and code is
cleaner.  Property instances associated with registered toplevel
extensions are used to enforce requirements like any other
object.

Added some unit tests specifically for property cleaning for
extensions.

Property order (for those contexts where it matters) is updated
to be spec-defined, toplevel extension, custom.
2021-07-06 14:27:40 -04:00
..
v20 Bug fixes, hackage removal, and some pre-commit stylistic 2021-06-30 17:50:00 -04:00
v21 Make extension instances work the same as other objects, with 2021-07-06 14:27:40 -04:00
__init__.py
test_hashes.py Add back usage of spec_version where HashesProperty is used for 2021-03-31 16:20:33 -04:00
test_pattern_equivalence.py pre-commit stylistic fix 2021-02-04 17:33:25 -05:00
test_properties.py pre-commit stylistic fix 2021-04-14 12:58:09 -04:00
test_spec_version_detect.py Improve is_sdo() et al utility functions with respect to 2021-01-20 16:59:39 -05:00
test_utils_type_checks.py pre-commit stylistic fixes 2021-01-20 20:49:01 -05:00
test_workbench.py Initial revamp of customization enforcement and detection. 2021-03-31 15:21:55 -04:00