github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-11-22 12:42:16 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
7be556fc19
discourse/.prettierignore

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

26 lines
693 B
Plaintext
Raw Normal View History

DEV: adds prettier (#5956) Run `prettier --write "app/assets/stylesheets/**/*.scss" "plugins/**/*.scss"` after making sure you installed it with `yarn` It's recommended to configure your editor to run prettier on file save.
2018-06-08 17:49:31 +08:00
app/assets/stylesheets/vendor/
plugins/**/assets/stylesheets/vendor/
DEV: Ensure prettier uses the same patterns everywhere
2020-08-20 18:36:52 +08:00
plugins/**/assets/javascripts/vendor/
adds package.json to prettier ignore list
2018-07-04 16:35:40 +08:00
package.json
DEV: unpin Prettier version, apply to YAML files We had Prettier pinned because of https://github.com/prettier/prettier/issues/5529. Since that bug is fixed, unpinning. Prettier now supports YAML, so this applies Prettier to all .yml except for translations, which should not be edited directly anyway.
2019-01-18 02:05:39 +08:00
config/locales/**/*.yml
DEV: Prettify *.en_US.yml files
2019-05-21 05:21:43 +08:00
!config/locales/**/*.en*.yml
FIX: Importing of polls from phpBB3 was broken Follow-up to 24369a81
2019-05-06 18:37:19 +08:00
script/import_scripts/**/*.yml
DEV: Don't lint core files when target == plugins (#10259) * DEV: Don't lint core files when target == plugins * Prettier the plugin/*.js files * Update eslintignore/prettierignore * Add eslint-plugin-ember and eslint-plugin-node * Properly lint all js files in all plugins * LINT: run prettier on test/*.js files * DEV: Run prettier checks on test/*.js files * ESLint plugins' assets/javascripts and test/javascripts directories only
2020-08-25 17:40:40 +08:00
app/assets/javascripts/env.js
app/assets/javascripts/main_include_admin.js
app/assets/javascripts/vendor.js
app/assets/javascripts/locales/i18n.js
app/assets/javascripts/ember-addons/
app/assets/javascripts/discourse/lib/autosize.js
lib/javascripts/locale/
lib/javascripts/messageformat.js
lib/highlight_js/
plugins/**/lib/javascripts/locale
public/
vendor/
app/assets/javascripts/discourse/tests/test_helper.js
app/assets/javascripts/discourse/tests/fixtures
node_modules/
dist/
PERF: backoff background requests when overloaded (#10888) When the server gets overloaded and lots of requests start queuing server will attempt to shed load by returning 429 errors on background requests. The client can flag a request as background by setting the header: `Discourse-Background` to `true` Out-of-the-box we shed load when the queue time goes above 0.5 seconds. The only request we shed at the moment is the request to load up a new post when someone posts to a topic. We can extend this as we go with a more general pattern on the client. Previous to this change, rate limiting would "break" the post stream which would make suggested topics vanish and users would have to scroll the page to see more posts in the topic. Server needs this protection for cases where tons of clients are navigated to a topic and a new post is made. This can lead to a self inflicted denial of service if enough clients are viewing the topic. Due to the internal security design of Discourse it is hard for a large number of clients to share a channel where we would pass the full post body via the message bus. It also renames (and deprecates) triggerNewPostInStream to triggerNewPostsInStream This allows us to load a batch of new posts cleanly, so the controller can keep track of a backlog Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com>
2020-10-13 13:56:03 +08:00
**/*.rb
Reference in New Issue Copy Permalink