Breeze does not support sending the displayName as metadata

0
votes

One of the things why really enjoy working with Breeze is because I have a lot of freedom regarding the metadata, and I use this freedom to manually provide an entity model, including validators. This works great, but when it comes to localizing the messages for the standard validators, I noticed that they use the property names instead of the display names, and this was because I set the display names after the metadata was loaded from server. Well, the thing is that I want to avoid a second call to server just to get the display names. As a temporary solution, I changed the breeze code to allow getting the displayName also from the metadata sent from server, but then again, I do not like changing the breeze sources.

Is there any other way of getting the metadata in one call and provide it to breeze? Naturally, other information like Description or Watermark would be welcome.

The latest versions provide a custom node, which I could use, but then I need some sort of interceptor for each property, where I take the display name and set it to the data and navigation properties. Is there a way to do this?

Remarks: I have a pull request on github for the breeze project, the changes are minimal.

1
metadatabreeze

1 Answers

0
votes

Presumably you've read about Breeze's "custom" metadata support: http://www.breezejs.com/documentation/custom-metadata

If so, then all you need to do is create a custom endpoint on the server that creates json in the 'custom metadata' format (you will probably use reflection on the server to collect this data), and return this json to the client and then call

myMetadataStore.importMetadata(customMetadataFromServer, true);