snapshot of https://github.com/mattermost/mattermost.git (master, 2026-09-16; blobs > 131072B omitted)

e2e-tests/cypress/tests/fixtures/mm_file_testing/Code/JSON

@@ -0,0 +1,80 @@
+{ 
+  "fathers" : [ 
+    { 
+      "id" : 0,
+      "married" : false,
+      "name" : "Gary Johnson",
+      "sons" : null,
+      "daughters" : [ 
+        { 
+          "age" : 7,
+          "name" : "Laura"
+          },
+        { 
+          "age" : 1,
+          "name" : "Karen"
+          }
+        ]
+      },
+    { 
+      "id" : 1,
+      "married" : true,
+      "name" : "Michael Taylor",
+      "sons" : null,
+      "daughters" : [ 
+        { 
+          "age" : 13,
+          "name" : "Sandra"
+          },
+        { 
+          "age" : 7,
+          "name" : "Cynthia"
+          },
+        { 
+          "age" : 8,
+          "name" : "Mary"
+          }
+        ]
+      },
+    { 
+      "id" : 2,
+      "married" : false,
+      "name" : "Steven Martin",
+      "sons" : null,
+      "daughters" : [ 
+        { 
+          "age" : 16,
+          "name" : "Betty"
+          }
+        ]
+      },
+    { 
+      "id" : 3,
+      "married" : true,
+      "name" : "Ronald Gonzalez",
+      "sons" : null,
+      "daughters" : [
+        ]
+      },
+    { 
+      "id" : 4,
+      "married" : false,
+      "name" : "Paul Taylor",
+      "sons" : null,
+      "daughters" : [ 
+        { 
+          "age" : 27,
+          "name" : "Laura"
+          }
+        ]
+      },
+    { 
+      "id" : 5,
+      "married" : false,
+      "name" : "Gary Smith",
+      "sons" : null,
+      "daughters" : [
+        ]
+      }
+    ]
+  }

e2e-tests/cypress/tests/fixtures/mm_file_testing/Code/Patch.diff

@@ -0,0 +1,10 @@
+--- hello.c	2014-10-07 18:17:49.000000000 +0530
++++ hello_new.c	2014-10-07 18:17:54.000000000 +0530
+@@ -1,5 +1,6 @@
+ #include <stdio.h>
+ 
+-int main() {
++int main(int argc, char *argv[]) {
+ 	printf("Hello World\n");
++	return 0;
+ }

e2e-tests/cypress/tests/fixtures/mm_file_testing/Code/Python

@@ -0,0 +1,18 @@
+from time import localtime
+
+activities = {8: 'Sleeping',
+              9: 'Commuting',
+              17: 'Working',
+              18: 'Commuting',
+              20: 'Eating',
+              22: 'Resting' }
+
+time_now = localtime()
+hour = time_now.tm_hour
+
+for activity_time in sorted(activities.keys()):
+    if hour < activity_time:
+        print activities[activity_time]
+        break
+else:
+    print 'Unknown, AFK or sleeping!'

e2e-tests/cypress/tests/fixtures/mm_file_testing/Documents/Text.txt

@@ -0,0 +1,116 @@
+=== Plugin Name ===
+Contributors: (this should be a list of wordpress.org userid's)
+Donate link: http://example.com/
+Tags: comments, spam
+Requires at least: 3.0.1
+Tested up to: 3.4
+Stable tag: 4.3
+License: GPLv2 or later
+License URI: http://www.gnu.org/licenses/gpl-2.0.html
+
+Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.
+
+== Description ==
+
+This is the long description.  No limit, and you can use Markdown (as well as in the following sections).
+
+For backwards compatibility, if this section is missing, the full length of the short description will be used, and
+Markdown parsed.
+
+A few notes about the sections above:
+
+*   "Contributors" is a comma separated list of wordpress.org usernames
+*   "Tags" is a comma separated list of tags that apply to the plugin
+*   "Requires at least" is the lowest version that the plugin will work on
+*   "Tested up to" is the highest version that you've *successfully used to test the plugin*. Note that it might work on
+higher versions... this is just the highest one you've verified.
+*   Stable tag should indicate the Subversion "tag" of the latest stable version, or "trunk," if you use `/trunk/` for
+stable.
+
+    Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so
+if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that'll be used
+for displaying information about the plugin.  In this situation, the only thing considered from the trunk `readme.txt`
+is the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in
+your in-development version, without having that information incorrectly disclosed about the current stable version
+that lacks those changes -- as long as the trunk's `readme.txt` points to the correct stable tag.
+
+    If no stable tag is provided, it is assumed that trunk is stable, but you should specify "trunk" if that's where
+you put the stable version, in order to eliminate any doubt.
+
+== Installation ==
+
+This section describes how to install the plugin and get it working.
+
+e.g.
+
+1. Upload the plugin files to the `/wp-content/plugins/plugin-name` directory, or install the plugin through the WordPress plugins screen directly.
+1. Activate the plugin through the 'Plugins' screen in WordPress
+1. Use the Settings->Plugin Name screen to configure the plugin
+1. (Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes)
+
+
+== Frequently Asked Questions ==
+
+= A question that someone might have =
+
+An answer to that question.
+
+= What about foo bar? =
+
+Answer to foo bar dilemma.
+
+== Screenshots ==
+
+1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
+the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets 
+directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png` 
+(or jpg, jpeg, gif).
+2. This is the second screen shot
+
+== Changelog ==
+
+= 1.0 =
+* A change since the previous version.
+* Another change.
+
+= 0.5 =
+* List versions from most recent at top to oldest at bottom.
+
+== Upgrade Notice ==
+
+= 1.0 =
+Upgrade notices describe the reason a user should upgrade.  No more than 300 characters.
+
+= 0.5 =
+This version fixes a security related bug.  Upgrade immediately.
+
+== Arbitrary section ==
+
+You may provide arbitrary sections, in the same format as the ones above.  This may be of use for extremely complicated
+plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or
+"installation."  Arbitrary sections will be shown below the built-in sections outlined above.
+
+== A brief Markdown Example ==
+
+Ordered list:
+
+1. Some feature
+1. Another feature
+1. Something else about the plugin
+
+Unordered list:
+
+* something
+* something else
+* third thing
+
+Here's a link to [WordPress](http://wordpress.org/ "Your favorite software") and one to [Markdown's Syntax Documentation][markdown syntax].
+Titles are optional, naturally.
+
+[markdown syntax]: http://daringfireball.net/projects/markdown/syntax
+            "Markdown is what the parser uses to process much of the readme file"
+
+Markdown uses email style notation for blockquotes and I've been told:
+> Asterisks for *emphasis*. Double it up  for **strong**.
+
+`<?php code(); // goes in backticks ?>`

e2e-tests/cypress/tests/fixtures/mm_file_testing/Documents/XML.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<mattermost>
+    <server>
+        <name>Test Server</name>
+        <version>10.12.0</version>
+        <features>
+            <feature enabled="true">code_preview</feature>
+            <feature enabled="true">file_attachments</feature>
+            <feature enabled="false">legacy_support</feature>
+        </features>
+    </server>
+    <channels>
+        <channel id="1" type="public">
+            <name>Town Square</name>
+            <display_name>Town Square</display_name>
+            <purpose>General discussion</purpose>
+        </channel>
+        <channel id="2" type="private">
+            <name>off-topic</name>
+            <display_name>Off-Topic</display_name>
+            <purpose>Non-work topics</purpose>
+        </channel>
+    </channels>
+    <metadata>
+        <created_at>2025-10-09T12:00:00Z</created_at>
+        <updated_at>2025-10-09T12:30:00Z</updated_at>
+    </metadata>
+</mattermost>