You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "James Carman (JIRA)" <ji...@apache.org> on 2008/09/13 01:05:46 UTC

[jira] Commented: (WICKET-1830) Include Component Path in Generated Markup

    [ https://issues.apache.org/jira/browse/WICKET-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630707#action_12630707 ] 

James Carman commented on WICKET-1830:
--------------------------------------

As I mentioned in the email thread, I'd like to try to take a stab at this one.  I'll try to submit a patch soon.

> Include Component Path in Generated Markup
> ------------------------------------------
>
>                 Key: WICKET-1830
>                 URL: https://issues.apache.org/jira/browse/WICKET-1830
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>            Reporter: James Carman
>            Priority: Minor
>
> For unit testing purposes, it would be nice to know the exact ids of the components on your wicket pages.  Perhaps the generated markup could contain a wicket:path attribute?
> <div wicket:path="some:path:to:this:div">

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.