Skip to content

Drop qmlobjdef, support deep subproperties in qmlprop - #17

Closed
ChALkeR wants to merge 1 commit into
masterfrom
drop-qmlobjdef
Closed

Drop qmlobjdef, support deep subproperties in qmlprop#17
ChALkeR wants to merge 1 commit into
masterfrom
drop-qmlobjdef

Conversation

@ChALkeR

@ChALkeR ChALkeR commented Jul 3, 2016

Copy link
Copy Markdown
Member

qmlobjdef supported only two components, a different format was needed to support assignments like Drag.hotSpot.x: width / 2.

Let's just use qmlprop with name = 'Drag.hotSpot.x' for that, instead of defining a separate token type for properties with two components.

Refs: qmlweb/qmlweb#280

/cc @akreuzkamp

qmlobjdef supported only two components, a different format was needed to
support assignments like Drag.hotSpot.x: width / 2.

Let's just use qmlprop with name = 'Drag.hotSpot.x' for that, instead of
defining a separate token type for properties with two components.

Refs: qmlweb/qmlweb#280
@stephenmdangelo

Copy link
Copy Markdown
Member

+1 This (and the corresponding change in qmlweb) fixes parsing of a use-case I have that's setting a module-qualified attached property (e.g. ModuleQualifer.AttachedObject.property: "foo").

@akreuzkamp

Copy link
Copy Markdown
Member

I'm not 100% convinced to be honest. Wouldn't it be better to create proper AST for the names?
See #19 for an alternative approach, that creates proper AST.

@ChALkeR

ChALkeR commented Jul 9, 2016

Copy link
Copy Markdown
Member Author

Closing in favor of #19.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants