okapiframework / Okapi / issues / #603 - Option to not have leading slash on JSONFilter path-type text unit ids — Bitbucket

Issue #603 resolved

YvesS created an issue 2017-03-23

The JSON filter can use an JSONPath-like path as the ID of the text unit. It is in the form: /name1/name2/name3

There is a need for the same value but without the leading /. For example: would give menu/popup/menuitem instead of /menu/popup/menuitem See https://groups.yahoo.com/neo/groups/okapitools/conversations/messages/5334 for details.

This should be an option (not set by default).

Comments (4)

YvesS reporter
- edited description
- 2017-03-23T18:53:25+00:00
YvesS reporter
- changed title to Option to not have leading slash on JSONFilter path-type text unit ids
- 2017-03-23T18:55:31+00:00
Former user Account Deleted
- changed status to resolved
JSONFilter: Adding checkbox to include leading '/' when using JSON key paths as TU IDs. Resolving issue ~~#603~~.

→ <<cset 6810cee79274>>
- 2017-04-24T23:53:40+00:00
YvesS reporter
Merged in jsonLeadingSlash (pull request #160) Resolving issue ~~#603~~

→ <<cset 7034cafdefd7>>
- 2017-04-25T11:46:28+00:00
Log in to comment

Assignee: Former user

Type: enhancement

Priority: minor

Status: resolved

Milestone: –

Version: –

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!