-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add 4DForm as a JSON language #4639
Conversation
4DForm extension contains a description in JSON format of a form in the 4D software language.
4DForm extension contain JSON data. This example is a real form used as a demonstration during a 4D training.
form.4DForm will be the most common file name when using 4DForm extension as this is automatically created by the 4D Software.
This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions. |
lib/linguist/languages.yml
Outdated
@@ -2337,6 +2338,7 @@ JSON: | |||
- ".tern-project" | |||
- ".watchmanconfig" | |||
- composer.lock | |||
- form.4DForm |
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.
This shouldn't be necessary as you already added .4DForm
as a JSON extension.
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.
Ok I was not sure If I had to add it in the filename too.
.4DForm is already a JSON extension
@Alhadis Did you already check usage? Each repository seems to hold a lot of files. |
Crap, you're right. There are only 28 repositories:
Not nearly enough... |
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.
Hi, thanks for the interest and the check. Effectively, the non-beta (v18) should be released in early 2020. We could expect an increasing number of directories in the mid-2020. I also think that a lot of repositories may be private and are therefore not measurable. |
This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions. |
@Ganbin I usually check usage every ~6 months and stop monitoring file extensions for which usage hasn't grown. So it's maybe best if I start checking around the time the non-beta is released... Could you post here when that happens? |
@pchaigno Ok I will try to remember to post here in about 6 month when the non-beta will be released. |
This pull request has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this pull request was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions. |
This pull request has been automatically closed because it has not had activity in a long time. Please feel free to reopen it or create a new issue. |
Description
4DForm extension contains JSON data representing 4D Form description. It is used in the context of 4D software application which start to provide source control compatibility in beta within the new v17 R6 version and will be released officially in v18 (between end 19 - begin 20). More and more repositories contains that kind of files.
Checklist: