Wicket
  1. Wicket
  2. WICKET-1830

Include Component Path in Generated Markup

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.3.5, 1.4-RC1
    • Component/s: wicket
    • Labels:
      None

      Description

      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">

        Issue Links

          Activity

          Igor Vaynberg made changes -
          Link This issue relates to WICKET-2832 [ WICKET-2832 ]
          James Carman made changes -
          Comment [ Ok, cool. I did look through the source to try to figure out where this would go. I didn't find a nice quick and easy place to make this change. So, I didn't get around to it yet. Out of curiosity, do you have the SVN version number of your checkin? I'd love to see the code changes (I don't get SVN commit messages). ]
          Igor Vaynberg made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]
          Fix Version/s 1.4-M4 [ 12313295 ]
          Fix Version/s 1.3.5 [ 12313175 ]
          Igor Vaynberg made changes -
          Field Original Value New Value
          Assignee Igor Vaynberg [ ivaynberg ]
          James Carman created issue -

            People

            • Assignee:
              Igor Vaynberg
              Reporter:
              James Carman
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development