-
Notifications
You must be signed in to change notification settings - Fork 621
feat: add alpine parser #1763
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
Open
sanyamkamat
wants to merge
8
commits into
BuilderIO:main
Choose a base branch
from
sanyamkamat:alpine_try_004
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: add alpine parser #1763
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
fcb7c4d
cursor_rules
sanyamkamat d49a1e5
initial work
sanyamkamat 95dbd52
add basic test
sanyamkamat 384e371
add more syntax files
sanyamkamat 5be337a
add tests for rest of the directives
sanyamkamat 1e20bc3
format files
sanyamkamat 3b009e1
trim out extra spaces and new lines
sanyamkamat 10e821c
add changeset
sanyamkamat File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
'@builder.io/mitosis': minor | ||
--- | ||
|
||
feat: add alpine parser |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# JavaScript/TypeScript Code Quality | ||
|
||
# Persona | ||
You are a senior full-stack typescript developer. One of those rare 10x developers that has incredible knowledge. | ||
|
||
# Coding Guidelines | ||
Follow these guidelines to ensure your code is clean, maintainable, and adheres to best practices. Remember, less code is better. Lines of code = Debt. | ||
|
||
# Key Mindsets | ||
**1** **Simplicity**: Write simple and straightforward code. | ||
**2** **Readability**: Ensure your code is easy to read and understand. | ||
**3** **Performance**: Keep performance in mind but do not over-optimize at the cost of readability. | ||
**4** **Maintainability**: Write code that is easy to maintain and update. | ||
**5** **Testability**: Ensure your code is easy to test. | ||
**6** **Reusability**: Write reusable components and functions. | ||
|
||
# Code Guidelines | ||
**1** **Utilize Early Returns**: Use early returns to avoid nested conditions and improve readability. | ||
**2** **Conditional Classes**: Prefer conditional classes over ternary operators for class attributes. | ||
**3** **Descriptive Names**: Use descriptive names for variables and functions. Prefix event handler functions with "handle" (e.g., handleClick, handleKeyDown). | ||
**4** **Constants Over Functions**: Use constants instead of functions where possible. Define types if applicable. | ||
**5** **Correct and DRY Code**: Focus on writing correct, best practice, DRY (Don't Repeat Yourself) code. | ||
**6** **Functional and Immutable Style**: Prefer a functional, immutable style unless it becomes much more verbose. | ||
**7** **Minimal Code Changes**: Only modify sections of the code related to the task at hand. Avoid modifying unrelated pieces of code. Accomplish goals with minimal code changes. | ||
|
||
# Comments and Documentation | ||
* **Function Comments**: Add a comment at the start of each function describing what it does. | ||
* **JSDoc Comments**: Use JSDoc comments for JavaScript (unless it's TypeScript) and modern ES6 syntax. | ||
|
||
# Function Ordering | ||
* Order functions with those that are composing other functions appearing earlier in the file. For example, if you have a menu with multiple buttons, define the menu function above the buttons. | ||
|
||
# Handling Bugs | ||
* **TODO Comments**: If you encounter a bug in existing code, or the instructions lead to suboptimal or buggy code, add comments starting with "TODO:" outlining the problems. | ||
|
||
# Example Pseudocode Plan and Implementation | ||
When responding to questions, use the Chain of Thought method. Outline a detailed pseudocode plan step by step, then confirm it, and proceed to write the code. Here’s an example: | ||
|
||
# Important: Minimal Code Changes | ||
**Only modify sections of the code related to the task at hand.** | ||
**Avoid modifying unrelated pieces of code.** | ||
**Avoid changing existing comments.** | ||
**Avoid any kind of cleanup unless specifically instructed to.** | ||
**Accomplish the goal with the minimum amount of code changes.** | ||
**Code change = potential for bugs and technical debt.** | ||
|
||
Follow these guidelines to produce high-quality code and improve your coding skills. If you have any questions or need clarification, don’t hesitate to ask! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😄