Currently {@code ContextResultURIConverterFactory} is used in two differentcontexts, and it receives critically different information as {@code flags}argument for each context.
Using single interface in semantically different contexts leads to a lot of confusion and awkward code. Redesign is highly desired. Current plan is to do away with usage 2, and design better interface for usage 1.
@author brad @see ReplayParseContext#makeConverter @see AccessPointAdapter#getUriConverter
|
|
|
|
|
|
|
|
|
|