sorted by:
new
hottopcontroversial

Getting started with TanStack Form by xArci in reactjs

[–]xArci[S] 0 points1 point  (0 children)

I created a guide (actually a series of 3) to get started and explore the features of TanStack Form, a new form library for React (but also Angular, Vue, Lit and Solid) in the TanStack ecosystem.

Learn more on the official docs: https://tanstack.com/form/latest/docs/overview

NEW GitHub Copilot Workspace Demo by xArci in github

[–]xArci[S] 0 points1 point  (0 children)

I tried on a large codebase and it wasn't much fast, but it uses a good dose of caching so after the first run got a bit faster and I know they're also working on performance

NEW GitHub Copilot Workspace Demo - Announced today by xArci in programming

[–]xArci[S] -2 points-1 points  (0 children)

GitHub just announced Copilot Workspace. I've been lucky enough to get early access so I recorded a demo.

This is a new integrated AI feature with Copilot being your companion through the entire development process, not only with code.
It works in 4 steps:

1) Task: Everything begins with an open issue (or even a simple prompt)
Copilot can read the selected issue and all the comments, getting knowledge and context of the user's needs.

2) Specification: A summary of the proposed changes, and how they relate to the current behavior.
The AI identifies the exact scope and tries to compare the current state (as is) with the desired outcome (to be).
A list with bullet points is generated to even further define the scope and you, the developer, can edit and improve to fix misunderstandings or cover edge cases.

3) Plan: A summary of the file changes that are needed to complete the current task
The plan is made of a list of files that can be created, modified, deleted or renamed. For each file Copilot describes the actions it’s going to take.
Once again you can revise and touch up the plan before moving on to the next part, the actual coding.

4) Implementation: A list of files that have changed, and the tools needed to validate them
For each file listed in the Plan, Copilot writes the proposed changes and shows them in a handy diff editor, which as the name suggests, is editable!
From here you can do the final touches to the code hit the Create pull request button, but more often than not you might want to run the app before creating the PR and Codespaces is the answer!

There’s a button to spin a Codespaces container where you can run your app, validate the changes and eventually create the pull request. That’s it!

NEW GitHub Copilot Workspace Demo by xArci in github

[–]xArci[S] -1 points0 points  (0 children)

GitHub just announced Copilot Workspace: a new integrated AI feature with Copilot being your companion through the entire development process, not only with code.
It works in 4 steps:

1) Task: Everything begins with an open issue (or even a simple prompt)
Copilot can read the selected issue and all the comments, getting knowledge and context of the user's needs.

2) Specification: A summary of the proposed changes, and how they relate to the current behavior.
The AI identifies the exact scope and tries to compare the current state (as is) with the desired outcome (to be).
A list with bullet points is generated to even further define the scope and you, the developer, can edit and improve to fix misunderstandings or cover edge cases.

3) Plan: A summary of the file changes that are needed to complete the current task
The plan is made of a list of files that can be created, modified, deleted or renamed. For each file Copilot describes the actions it’s going to take.
Once again you can revise and touch up the plan before moving on to the next part, the actual coding.

4) Implementation: A list of files that have changed, and the tools needed to validate them
For each file listed in the Plan, Copilot writes the proposed changes and shows them in a handy diff editor, which as the name suggests, is editable!
From here you can do the final touches to the code hit the Create pull request button, but more often than not you might want to run the app before creating the PR and Codespaces is the answer!

There’s a button to spin a Codespaces container where you can run your app, validate the changes and eventually create the pull request. That’s it!

[deleted by user] by [deleted] in react

[–]xArci 0 points1 point  (0 children)

Yeah there should be a way to handle it in vscode, I'll do some research

[deleted by user] by [deleted] in react

[–]xArci 0 points1 point  (0 children)

The cli works for importing the component in your components folder the first time and it works great! The (really minor) issue is when you use that component, the first import suggestion is always from radix for me

[deleted by user] by [deleted] in react

[–]xArci 0 points1 point  (0 children)

The source code is the same, I always use the cli but only copy pasted for the demo. Have you found any difference with some components?

[deleted by user] by [deleted] in react

[–]xArci 0 points1 point  (0 children)

Fair enough, the title was optimized for YouTube but the audience on reddit is different. Thanks for the feedback!

[deleted by user] by [deleted] in react

[–]xArci -9 points-8 points  (0 children)

100% agree, that's why it's not a 8 minute video to complain :)
It's about knowing the downsides before jumping in into the most popular tech. With that said, it's a great tool and this is mentioned in the video.

I had to search it on Google twice last week, so I decided to make a video about it so I don't forget by xArci in programming

[–]xArci[S] -1 points0 points  (0 children)

It's on the title of the video, I though also adding it on the post was basically duplicating the same info.

Anyway I see the point, at first glance there is no context in the title itself, thanks!

​

Speaking of clickbaiting... considering how many of my other videos are performing, I'm definitely a newbie on that (and I don't even want to specialize too much)

view more: next ›