When user send a configuration, the way they write strings can vary a little (case, space, …). Strings are often used as an index. If we want the user to have some flexibility, index matching should be non-strict (fuzzy).
Example
Skylake is a cpu family
Request :
"cpu":{
"core_units":8,
"cpu_family":"Skylake"
}
But it could be written in different ways : skylake, Skylak, sky lake . We need all of those to match Skylake index.
Solution
Replace strict string matching to fuzzy matching in boaviztapi/model/component for CPU, RAM and SSD in smart_complete.
Problem
When user send a configuration, the way they write strings can vary a little (case, space, …). Strings are often used as an index. If we want the user to have some flexibility, index matching should be non-strict (fuzzy).
Example
Skylake
is a cpu familyRequest :
But it could be written in different ways :
skylake
,Skylak
,sky lake
. We need all of those to matchSkylake
index.Solution
Replace strict string matching to fuzzy matching in
boaviztapi/model/component
for CPU, RAM and SSD insmart_complete
.