What is the current behavior?

• Props typed as custom interfaces (e.g., Action) get classified as MEMBER_FLAGS.Unknown and receive no JSON parsing
• JSON-like string attributes for custom types remain as strings, making the prop undefined when accessed as an object
• Inconsistent behavior: string props sometimes get JSON parsing during hydration, but custom types never do
• Example: <my-cmp data='{"param":"value"}'></my-cmp> with @Prop() data: Action results in this.data being undefined

What is the new behavior?

• Custom interface props (MEMBER_FLAGS.Unknown) and any props (MEMBER_FLAGS.Any) now attempt JSON parsing when the string value looks like JSON (starts with {/[ and ends with }/])
• Primitive types (string, number, boolean) maintain their existing behavior - no JSON parsing
• Consistent behavior between SSR and non-SSR environments for custom types
• Graceful fallback: if JSON parsing fails, the original string value is preserved
• Example: <my-cmp data='{"param":"value"}'></my-cmp> with @Prop() data: Action now results in this.data being { param: "value" }

Does this introduce a breaking change?

• Yes
• No

Testing

Added