From the dotty branch,

++3.0.0-M1 core/compile

For now, ignore:

• Errors mentioning parboiled2 (#3761)
• Errors mentiong CollectionCompat (#3945)
• Errors mentioning literal macros (#3760)

What progress can we make? If they're indecipherable, can we begin to categorize them and make more tickets?

This is tedious work that won't land a feature during the Open Source event,

Currently, we manually append the params to the url / query string using urljoin. Instead, we can send the query params in as a dictionary

Hi, could you please provide some kind of mechanism how to say guardrail to follow openApi specification when generating code from swagger? Specifically I am talking about query parameters with array type (but there could be more differences), which are handled as multi (userId=1,userId=2) insted of default comma separated values (userIds=1,2). According to specification if there is no