Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One less warning with async #1208

Closed

Conversation

AnthonySteele
Copy link
Contributor

@AnthonySteele AnthonySteele commented Apr 21, 2020

Fixes / New Feature #

Proposed Changes

Remove a warning about the use of async without await:

Warning	CS1998	
This async method lacks 'await' operators and will run synchronously. 
Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.	
Ocelot.AcceptanceTests	C:\code\Ocelot\test\Ocelot.AcceptanceTests\ResponseCodeTests.cs	59	

@AnthonySteele
Copy link
Contributor Author

AnthonySteele commented Apr 21, 2020

I can look at more warnings to get familiar with the code, but I thought it best to start small.

Eventually you get to no warnings, so any regression to that stands out.

Some of them should probably be suppressed, e.g. IDE1006 ( naming ) in the tests and SA1413 ( trailing commas ) throughout.

@AnthonySteele AnthonySteele changed the title One less warning One less warning with async Apr 21, 2020
@raman-m raman-m changed the base branch from master to develop July 19, 2023 20:43
@raman-m
Copy link
Member

raman-m commented Jul 19, 2023

Anthony,
A lot of warning and compiler messages were fixed by my PR #1663 .

After merging develop branch with conflicts resolution, I took changes from develop branch because async was removed. We create PRs to develop now.
And now I don't see changes in diff at all.
Do you see? 😄

I believe this warning is gone now.
Could you confirm that please?

@raman-m
Copy link
Member

raman-m commented Jul 19, 2023

LoL 🤣
You've closed the PR!

Was it confirmation?

@raman-m raman-m added bug Identified as a potential bug wontfix No plan to include this issue in the Ocelot core functionality. labels Jul 19, 2023
@AnthonySteele
Copy link
Contributor Author

Yeah, it doesn't seem relevant any more (3 years ago?)

If we want to do this, it would be easier to start again. I don't have context after that time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identified as a potential bug wontfix No plan to include this issue in the Ocelot core functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants