TESTING : Added cursor rules & cursor ignore file #566
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.
What does this PR do?
Testing cursor IDE config scoped to a single project.
https://www.loom.com/share/becbe3af2be145338916a1223d39fa3a?sid=77e744b0-3dc0-415d-825e-c2a66d868f19
Cursor rules taken from our repos & from personal experience, comments on formatting from previous prs , & just some simply put guidelines I have gathered & put in a concise cursor rule files.
added cursor ignore to avoid going through some config files & in the case of oss-components, node modules. I do believe it will not be the case on upf-web for example, as we should allow it to explore upfluence dev dependencies at least.
DISCLAIMER: The generated component has no business going into the design system , I will remove it if we decide to move forward with cursor team wide & merge these cursor rules .
Related to: #
What are the observable changes?
Good PR checklist