Fix templateToSwaggerPath generates invalid path

[ch3rub1m]

Additional PR for #704 to avoid #1000

[codecov-io]

Codecov Report

Merging #1006 into master will increase coverage by 0.15%.
The diff coverage is 84%.

@@            Coverage Diff            @@
##           master   #1006      +/-   ##
=========================================
+ Coverage   53.84%     54%   +0.15%     
=========================================
  Files          42      42              
  Lines        4147    4170      +23     
=========================================
+ Hits         2233    2252      +19     
- Misses       1670    1672       +2     
- Partials      244     246       +2

Impacted Files	Coverage Δ
protoc-gen-swagger/genswagger/template.go	57.51% <84%> (+0.54%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8115cdb...163bea8. Read the comment docs.

[johanbrandhorst]

Thanks for this fix!

@tlyng Can you confirm this fixes your issue?

[johanbrandhorst]

Bump @tlyng, have you tested this fix?

[johanbrandhorst]

@ch3rub1m could you rebase this on master please? Lets get this fix merged.

[ch3rub1m]

@ch3rub1m could you rebase this on master please? Lets get this fix merged.

Ok, I'll do it.

[ch3rub1m]

@johanbrandhorst Have done.

[johanbrandhorst]

The online ui is still reporting some conflicts, are you sure you pushed it?

[ch3rub1m]

@johanbrandhorst Done.

[johanbrandhorst]

Thanks for your contribution!

[johanbrandhorst]

Unfortunately this was causing crashes for valid paths (such as get: "/api/v3/availabilityGroup/{xid}/parent"), so I've had to revert this: #1078. @ch3rub1m a new issue is being raised with more details, but we'll need a new version of this in.

[BinaryHexer]

@johanbrandhorst is a new version of this already merged? Because I am able to reproduce the underlying issue with the latest master.

[johanbrandhorst]

No, I don't think it was ever picked up again unfortunately. We'd love to have someone contribute another fix 😄.