{"id":8722,"date":"2014-05-07T17:17:53","date_gmt":"2014-05-07T15:17:53","guid":{"rendered":"http:\/\/fdt.powerflasher.com\/?p=8722"},"modified":"2014-05-07T17:17:53","modified_gmt":"2014-05-07T15:17:53","slug":"new-metadata-tags-settings","status":"publish","type":"post","link":"https:\/\/fdt.powerflasher.com\/blog\/2014\/05\/new-metadata-tags-settings\/","title":{"rendered":"New Metadata Tags Settings"},"content":{"rendered":"

In the new Metadata Tags Settings you can specific which Tags should be available and how strict they should be handled:
\n\"MetadataTagSettings\"<\/a>
\nFor example the Event<\/em> Metadata Tag has the two required parameters name<\/em> and type<\/em>. You can also add your own Metadata Tags.<\/p>\n

The Event<\/em> Metadata Tag appears as auto completion option with its parameters:
\n\"EventAC\"<\/a>
\nFor example you could add the following metadata tag:<\/p>\n

[ErrorMessage(name=\u201d\u201d, severity=\u201d\u201d)]<\/p>\n

It should mark a class that it could send error messages to a receiver. The parameter name<\/em> should be limited to a name containing only letters and digits and the severity<\/em> should only have values like Info<\/em>,Warning<\/em>, and Error<\/em>.<\/p>\n

You could achieve this by the following steps:<\/p>\n

  • Add a new Tag (Add Tag<\/em>).<\/li>\n
  • Click on the name of new appeared tag and enter the name ErrorMessage<\/em>.<\/li>\n
  • After pressing return the tag list is alphabetically reorder so that the tag ErrorMessage<\/em> appears below Embed<\/em>.<\/li>\n
  • Selected the ErrorMessage<\/em> tag and use Add Parameter<\/em> to create a new parameter.<\/li>\n
  • Rename the new parameter to name<\/em>.<\/li>\n
  • The new parameter name<\/em> should be of type String<\/em> and its mode should be Required<\/em>.<\/li>\n
  • Now click on the cell of column Special <\/em>for parameter name<\/em>.<\/li>\n
  • Here you can enter a java regular expression describing what kind of names are allowed. For more details about java regular expressions see:\n

    \nhttp:\/\/www.vogella.com\/tutorials\/JavaRegularExpressions\/article.html<\/a>
    \n    http:\/\/docs.oracle.com\/javase\/7\/docs\/api\/java\/util\/regex\/Pattern.html<\/a>\n<\/p>\n<\/li>\n

  • For identifiers without underscore the pattern [A-Za-z0-9]<\/em>+ should be adequate so we use it for the name<\/em> parameter.<\/li>\n
  • The second parameter severity<\/em> can be added the same way.<\/li>\n
  • The type of parameter severity<\/em> is String<\/em>, too.<\/li>\n
  • The pattern for value of parameter severity<\/em> should be: Info<\/em>|Warning<\/em>|Error<\/em><\/li>\n
  • We can assume that the severity<\/em> parameter is by default Error<\/em> so we can leave the parameter optional<\/em>.<\/li>\n
  • Since the ErrorMessage<\/em> tag should not contain any other parameter and requires at least the name<\/em> we switch it to Strict<\/em>.
    \n    \"ErrorMessageTagSettings\"<\/a>
    \nIn the lower area examples of how to use the metadata tag are shown and which checks are applied.<\/li>\n
  • Confirm your changes with Apply<\/em><\/li>\n

    Metadata Tags Settings can be set for each project inside project properties, too:
    \n    \"P\"<\/a>
    \nThese settings are stored inside the project settings folder as com.powerflasher.fdt.core.metaDataTags.prefs<\/em><\/p>\n

    Using Self-Defined Metadata Tags<\/h2>\n

    Here is an example how you could use the auto completion for the new example metadata tag ErrorMessage<\/em> as created above:
    \n    \"ErrorMessageAC\"<\/a><\/p>\n

    The default value for the parameters is the first possibility of the top most or-pattern if it is a simple constant.
    \n    \"ErrorMessageParameterAC\"<\/a><\/p>\n

    The auto completion for the severity<\/em> value offers all three values since they are simple constants appearing in the top most or-pattern of regular expression for parameter severity<\/em>:
    \n    \"ErrorMessageParameterValueAC\"<\/a><\/p>\n

    The severity<\/em>-parameter contains a not matching value and so an error is shown:
    \n    \"ErrorMessageWrongParameterValu\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

    In the new Metadata Tags Settings you can specific which Tags should be available and how strict they should be handled: For example the Event Metadata Tag has the two required parameters name and type. You can also add your own Metadata Tags. The Event Metadata Tag appears as auto completion option with its parameters: […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts\/8722"}],"collection":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/comments?post=8722"}],"version-history":[{"count":28,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts\/8722\/revisions"}],"predecessor-version":[{"id":8778,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/posts\/8722\/revisions\/8778"}],"wp:attachment":[{"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/media?parent=8722"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/categories?post=8722"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fdt.powerflasher.com\/blog\/wp-json\/wp\/v2\/tags?post=8722"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}