upstream/mercurial-mirror Files · rust/hg-core/src/operations/mod.rs

check-code: drop the check for whitespace around named parameters...

check-code: drop the check for whitespace around named parameters This check flags py3 annotations of named parameters, because `black` adds spaces around the assignment in this case. Since the chosen formatter has opinions (and pylint also wants the space in the case of annotations), drop the check so we can use py3 annotations.

Simon Sapin - - Load All Authors

File last commit:

r48882:bf8837e3 default


                r50465:3a2b6158

default

Download file

             mod.rs
        
                    11 lines
            
             | 447 B
            
                | application/rls-services+xml
            
             |
                RustLexer
            
             / rust / hg-core / src / operations / mod.rs
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      //! A distinction is made between operations and commands.

      //! An operation is what can be done whereas a command is what is exposed by

      //! the cli. A single command can use several operations to achieve its goal.

      mod cat;

      mod debugdata;

      mod list_tracked_files;

      pub use cat::{cat, CatOutput};

      pub use debugdata::{debug_data, DebugDataKind};

      pub use list_tracked_files::Dirstate;

      pub use list_tracked_files::{list_rev_tracked_files, FilesForRev};

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

				//! A distinction is made between operations and commands.
				//! An operation is what can be done whereas a command is what is exposed by
				//! the cli. A single command can use several operations to achieve its goal.

				mod cat;
				mod debugdata;
				mod list_tracked_files;
				pub use cat::{cat, CatOutput};
				pub use debugdata::{debug_data, DebugDataKind};
				pub use list_tracked_files::Dirstate;
				pub use list_tracked_files::{list_rev_tracked_files, FilesForRev};