You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice if the generator would use the correct file ending for generated components (.jsx instead of .js). This would have the benefit that editors (like Atom or Brackets) would be able to guess the file format correclty if they support jsx-syntax.
The text was updated successfully, but these errors were encountered:
thank you for your fast response. I think in this case it should at least be optional to use the .jsx (defaulting to .js).
When using CI-Tools (like SonarQube or linters like jsHint) files with jsx-syntax are not parseable and will therefore lead to errors that must be fixed in each of those various systems.
It would be nice if the generator would use the correct file ending for generated components (.jsx instead of .js). This would have the benefit that editors (like Atom or Brackets) would be able to guess the file format correclty if they support jsx-syntax.
The text was updated successfully, but these errors were encountered: