hackathoners suggestions

## abdellah aleoui

Hello Eren

Thank you so much for organizing this hackathon, it was an amazing experience

Regarding the questions:

1- in the case of my project, the thing that I found most helpful is that refine doesn't use DOM or browser-specific APIs in the core module, which makes it much easier for me to bring refine features to the native world without having to reinvent the wheel. of course, there was some exception like React query devtool and Telemetry, but it was easy to disable them from the configuration of the `<Refine>` component. (I also noticed that in a recent release, React query devtool is no longer included in the core module )
2- In my case, I didn't face any challenges related to refine itself; in fact, I found that refine simplifies a lot of things through its abstraction.
3- Here are some ideas that I think you could include in the devtool:
- Add the ability to cache or mock API responses, which can first make it easier for the user to test the application without sending a bunch of requests, and second, test backend changes before implementing them.
- Display a list of hooks and components used on each page with a link to access their docs easily.
- Give some suggestions and warnings in the case of the wrong usage of some hooks or components.
- Provide the user with a log function that can be used during development instead of the console.log and it will show the logs only in the devtool, which can help prevent showing the logs in production.

Again thank you so much for providing us with this great opportunity, and I'm looking forward to the next hackathon 🚀

## matheus
Hello there 👋
Thank you for the awesome event!

1. When I started working on my app, I had the idea and design in place but I didn't know what was the best approach to build the dashboard. At this moment refine helped me a lot. It gave me a fully fledged CRUD experience in seconds, so I could focus on the content.

2. I struggled with the refine documentation, I wish I didn't had to dive into multiple GitHub folders of the examples too often. There were also times when some specific information were "tucked" inside the multi-step tutorial.

3. I've already left a comment on the RFC Discussion on GitHub, but I'd like to see the code generated by inferencer inside the Devtools so that we could interact with it to experiment and fix some things.

A new suggestion not only for devtools but I'd like to see refine treated as a modular thing, so that we could at anytime swap ui frameworks, data providers, auth, etc...
I'd love to go from vite/react to headless/refine and keep doing flexible increments.

I am available for further comments and to help anytime.

Thanks,

## Luis Bertorelli
Hi there!

1- What were the things that you found most helpful in simplifying your work while building your project with refine?
The wizard was a great initial kickstart that saved me hours. After that, the basic CRUD views and all the boilerplate that were generated at the beginning of the project. Furthermore, the Inferencer allowed me to directly copy the code from the interface and insert it into the source code.

2- Which parts of the project did you find most challenging in your development process? Were there any specific features you wished refine had during your work?
The most challenging parts were understanding how I should work with Refine. It was the first time I used the framework, and I struggled because I couldn't find much information beyond the documentation. I believe that a guide explaining how to start from scratch with Refine would make understanding easier, as the amount of generated code can be a bit overwhelming, and the quick start doesn't cover everything that's in the boilerplate.

I didn't have many needs for extra features; I felt a greater need to understand how to accomplish tasks. However, there were two things I needed to do but couldn't:

a) The login component is very rigid; I wanted to have some kind of access below the username and password fields to insert an element, but I couldn't achieve that and ended up not implementing what I had in mind.

b) I would like more control over the error messages when submitting the form. The floating window that appears and disappears automatically is not ideal, especially when the message is too long to read in such a short time. Additionally, having a close button on the floating window would be helpful. In the case of my application, the inclusion process takes some time, so, if a user moves on to do something else and an error occurs, they would never know about it as the floating window closes automatically.

3- We are excited about launching a devtool in the near future to enhance refine's DevX. What features would you like to see included in this devtool?
It seems that the features you've already considered are sufficient. I couldn't think of anything more than that. However, maybe an overview of the component hierarchy, a tree illustrating the components in real-time, could be helpful.

Att,

## ondrej

Hey Eren,

I am glad I can participate in a hackathon. It was fun and very helpful journey.
For the question you have asked.
Definitely your docs. I was able to find all the information I needed.
Also the toolkit of refine like hooks for data fetching and Infercers for generating crud pages.
I have a bit of a problem with fetching data from supabase using aggregate operations, for example returning sum and count from sql query.
Also prefetching data on the server side when using infiniteQuery on client side causes troubles for typescript. However, the overall experience was great.
Well, that's really good information. I did not know this.
I think these two will be really helpful:
It will replace all of the console.log I have when inspecting what hooks are storing or returning.
Inspector/Monitor for data hooks and their details

Authentication and Authorization screens, showing the current status, previous calls, and provider details.

Again, thank you for the opportunity to participate.
Best regards,

S pozdravem,
Ondřej Šimanovský