jay-framework / jay-framework/jay
file extension recommendation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 3
- Avg merge
- 11m
- Merged PRs (30d)
- 5
Description
I made the mistake with Stylable and used the .st.css prefixed extension thinking I will get IDE features for the language.
I turns out more headache because all the other tool that know how to process the real extension like .css or .html now should ignore the .prefix.extension from the regular process.
For example react-react-app already has rules for css and when I wanted to add Stylable support I needed to add ignore rule in all the css process loader from .st.css
I think it will be better to use something like .jayhtml as the full extension for the template.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating how template and stylesheet extensions are recognized in the TypeScript framework and its React integration, then assess the proposed full extension against existing CSS and HTML processing; done would require a decided extension convention and updated integrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100