ADM-620:[frontend]fix: fix regular to swagger in middle

[BoBoDai]

Summary

...

Before

Description

Screenshots
If applicable, add screenshots to help explain behavior of your code.

After

Description

Screenshots
If applicable, add screenshots to help explain behavior of your code.

Note

Null

[github-actions]

Hi @BoBoDai! 👋
Thank you for submitting a pull request! We appreciate your contribution and will review your changes as soon as possible.

[guzhongren]

I think, we can't access swagger in the public network,
coc the React router of the frontend.
if you are right, please give us a screenshot in the PR, you can test it locally, not test it in SIT/PROD env.

[BoBoDai]

Ok,
In fact, our nginx has opened the backend interface. Normally, it can be accessed directly through "/api/v1/docs".
At local testing is also consistent with this situation.

nginx.conf

web

But we also have a regular location that will intercept all links with any file format suffix.

nginx.conf

web

If we add a regular for swagger, we can block the previous regular. After that, we can access swagger normally.

nginx.conf

web

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
+0.00%	∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (d568f08)	4333	4333	100.00%
Head commit (bc44d60)	8666 (+4333)	8666 (+4333)	100.00% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#793)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{You may notice some variations in coverage metrics with the latest Coverage engine update. For more details, visit the documentation}