summaryrefslogtreecommitdiff
path: root/redfish-core/include/resource_messages.hpp
diff options
context:
space:
mode:
authorEd Tanous <ed@tanous.net>2020-09-16 07:15:44 +0300
committerEd Tanous <ed@tanous.net>2020-09-22 23:42:36 +0300
commit02379d3572bc471ecbb75f33e5a03203c4b3e517 (patch)
tree933a6e9077cde7a16de5dcce5a85a25ce596b877 /redfish-core/include/resource_messages.hpp
parent684bb4b89f88b394b00b140d71c161143393f80b (diff)
downloadbmcweb-02379d3572bc471ecbb75f33e5a03203c4b3e517.tar.xz
Fix IBM management console to match coding standard
Lots of missing inline definitions, a case where a RVO move is not guaranteed when returning a variant, and removing the header checks, which means that these types of build errors wont happen in the future. Tested: Should be no impact, but could someone from the IBM team grab these changes and sanity check them? Signed-off-by: Ed Tanous <ed@tanous.net> Change-Id: Iea0a06b8e744542a7d08e38217718e7a969f2827
Diffstat (limited to 'redfish-core/include/resource_messages.hpp')
-rw-r--r--redfish-core/include/resource_messages.hpp6
1 files changed, 3 insertions, 3 deletions
diff --git a/redfish-core/include/resource_messages.hpp b/redfish-core/include/resource_messages.hpp
index 4ff1c86967..9826566e27 100644
--- a/redfish-core/include/resource_messages.hpp
+++ b/redfish-core/include/resource_messages.hpp
@@ -5,7 +5,7 @@ namespace redfish
namespace messages
{
-nlohmann::json ResourceChanged(void)
+inline nlohmann::json ResourceChanged(void)
{
return nlohmann::json{
{"EventType", "ResourceChanged"},
@@ -16,7 +16,7 @@ nlohmann::json ResourceChanged(void)
{"MessageSeverity", "OK"}};
}
-nlohmann::json ResourceCreated(void)
+inline nlohmann::json ResourceCreated(void)
{
return nlohmann::json{
{"EventType", "ResourceAdded"},
@@ -27,7 +27,7 @@ nlohmann::json ResourceCreated(void)
{"MessageSeverity", "OK"}};
}
-nlohmann::json ResourceRemoved(void)
+inline nlohmann::json ResourceRemoved(void)
{
return nlohmann::json{
{"EventType", "ResourceRemoved"},