format component and function

[JerryWu1234]

#2585

• I've read and followed the contributing guide on how to create great pull requests.
• I've updated the relevant documentation for any new or updated feature
• I've linked relevant GitHub issue with "Closes #"
• I've added a visual demonstration under the form of a screenshot or video

[JerryWu1234]

@Janpot does your review finish? Anything else ?

[Janpot]

Thank you, this is looking good! If you're up to it can you bring back the return types?

[JerryWu1234]

why not .
Let me fix it tomorrow

[JerryWu1234]

Thank you, this is looking good! If you're up to it can you bring back the return types?

Last PR you told me that you also want to format the function and the component.

And tell me any demand please tell me

[Janpot]

Thank you, this is great! I've removed the tryFormat function as we don't use it anymore.

I've added one more item in #2585. The bindings editor formats expressions, this is a bit more challenging since we run this in the browser, we'll have to read the config on the server and pass it to the frontend.

[JerryWu1234]

Thank you, this is great! I've removed the tryFormat function as we don't use it anymore.

I've added one more item in #2585. The bindings editor formats expressions, this is a bit more challenging since we run this in the browser, we'll have to read the config on the server and pass it to the frontend.

ok I will continue to follow up on this issue

[JerryWu1234]

Thank you, this is great! I've removed the tryFormat function as we don't use it anymore.

I've added one more item in #2585. The bindings editor formats expressions, this is a bit more challenging since we run this in the browser, we'll have to read the config on the server and pass it to the frontend.

@Janpot what way do we pass it to the frontend ? Could I create a new API or anything else？
do you have any demand?

[Janpot]

You could add a getPrettierConfig method in the project. No need to specify a file, just resolve the prettier config at the project root. Pass it to the frontend and use it the same way we do with getVersionInfo.