Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Object metadata does not indicate that the CFC is final

Description

// C.cfc final component {}
<cfscript> // test.cfm o = new C() writeDump(getMetadata(o)) </cfscript>

On ColdFusion, it has a boolean property final which is true. Should be the same on Lucee.

Note also on CF if the CFC is not final, then the property isn’t presented in the metadata at all. I don’t think that’s great and am taking it up with Adobe. Will confirm back here if they think this is action-worthy.

Environment

None

Activity

Show:

Pothys - MitrahSoft 2 August 2022 at 14:43

Now I've checked this ticket with the lucee latest build 6.0.0.223-SNAPSHOT. Now getMetaData/getComponentMetaData result includes the key-value final-true for the final components.

Zac Spitzer 2 August 2022 at 13:23

Pothys - MitrahSoft 18 August 2021 at 11:05

I added a fix and testcase to this ticket

Pull Request: https://github.com/lucee/Lucee/pull/1412

Pothys - MitrahSoft 17 August 2021 at 12:18

I've checked this ticket and confirmed the issue happened on lucee latest version 5.3.8.201-SNAPSHOT also. If we use the final component means there is no way to identify the component is final, getmetadata() result doesn't have a final key. ACF has a key {final:true} when the component is final.

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 13 August 2021 at 13:03
Updated 2 August 2022 at 14:43
Resolved 2 August 2022 at 14:43

Flag notifications