HW-52637 pay pal account second line

[vshcherbyna-epam]

No description provided.

[peter-joseph]

you don't need to check if it contains because maps will already do that for you when you call Map.put and I think put is good enough for this operation

[peter-joseph]

you can pre-initialize it no need to assemble it as it goes, like so

Map<String, String> doubleBraceMap  = new HashMap<String, String>() {{
    put("key1", "value1");
    put("key2", "value2");
}};

[peter-joseph]

you don't need to check if it contains because maps will already do that for you when you call Map.put and I think put is good enough for this operation

[vshcherbyna-epam]

right and in case of Map.put we should also need to verify the previous value.

[peter-joseph]

you can pre-initialize it no need to assemble it as it goes, like so

Map<String, String> doubleBraceMap  = new HashMap<String, String>() {{
    put("key1", "value1");
    put("key2", "value2");
}};

[fmattos-hw]

@vshcherbyna-epam I really appreciate the effort and the robustness of the strategy pattern you introduced but I'd like to use a more simplistic approach. Creating an abstraction and managing instances with the map overcomplicate things and adds memory footprint in the app
Please expose a method in TransferMethodUtil class named getTransferMethodDetail(String): String use a switch case and return the correct value based on each transfer method type and empty in the default case

[vshcherbyna-epam]

@fmattos-hw, @peter-joseph, @azakrevska-epam
Sorry, I have obstacles to merge it onto the /development and back onto /origing, so Im going to create the new PR here: #44.